@pholien feng I need more detail on what you are seeing. There are two parts to accessing a secured NiFi installation, Authentication and authorization. Authentication by default expects users to authenticate using SSL. A user would need to present a valid certificate via their browser to NiFi for authentication. NiFi can also be configured via the login-identity.providers.xml file to support either LDAP or Kerberos for users authentication. After a user successfully authenticates, the authorization piece occurs. The above answer deals with the authorization piece only. Check you nifi-user.log to see if authentication is successful. make sure the DN shown in the nifi-users.log matches exactly (case sensitive and whitespace issues?) what is configured in the "Initial Admin Identity" property in your authorizers.xml file. When nifi is started for the first time after enabling https the users.xml and authorizations.xml files are generated based on the user supplied configurations in the authorizers.xml file. Should the configurations in the authorizers.xml get edited at a later time, those changes will not be made to the existing users.xml or authorizations.xml files. They are only ever created once, subsequent edits to these files are expected to be done via the NiFi application. If you made a mistake in these files when setting up https access for the first time, you can remove these two files and they we be re-created next time you start NiFi. Thanks, Matt
... View more
