Member since
02-27-2017
19
Posts
4
Kudos Received
0
Solutions
03-08-2017
02:16 PM
Good to hear.
... View more
03-06-2017
05:10 PM
2 Kudos
@Ayaskant Das NiFi by default will use a user's SSL certificate if it is included by your browser during the connection to NiFi's URL. NiFi can be configured to use LDAP or Kerberos as alternate Authentication methods. Once configured, these alternate methods will be used only if a user does not pass a SSL certificate. Information about setting up LDAP or kerberos can be found in NiFo's Admin guide: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#user-authentication Thanks, Matt
... View more
03-06-2017
06:14 PM
1 Kudo
You need to configure NiFi to use a login identity provider such as LDAP or Kerberos, and then navigate to the secure URL of the NiFi web ui, for example https://localhost:8443/nifi. If you have a certificate in your browser and get prompted, make sure to decline otherwise it will use that to authenticate. There are many reasons covering how to configure LDAP or Kerberos: https://pierrevillard.com/2017/01/24/integration-of-nifi-with-ldap/ http://bryanbende.com/development/2016/08/31/apache-nifi-1.0.0-kerberos-authentication https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html
... View more
02-12-2019
11:43 AM
@Joe P did you set up https i.e. did you enable SSL on the server?
... View more
05-05-2017
12:22 PM
@Ayaskant Das Just wondering if the above was able to resolve your issue. The nifi-user.log screenshot you provided clearly shows that you have reached NiFi and successfully authenticated with the above user DN; however, the user is not authorized to access the nifi /flow resource. Thank you, Matt In order for users to get notifications of a comment to a post you must tag them in teh response using the @<username> (example: @Matt Clarke )
... View more