What authorization configuration have you provided? When SSL/TLS is enabled for NiFi, it no longer allows anonymous access to the UI and API. Users must authenticate and then be authorized to have access to the flow controller, processors, etc. By default, NiFi uses TLS client authentication (i.e. the browser provides a client certificate) to perform authentication, and a simple file-based authorizer for authorization. If you wish, you can configure Kerberos (via login form or SSO), or LDAP(S) for access control.
Bryan Bende has written a very helpful guide for performing the entire process here [1]. [1] http://bryanbende.com/development/2016/08/17/apache-nifi-1-0-0-authorization-and-multi-tenancy <http://bryanbende.com/development/2016/08/17/apache-nifi-1-0-0-authorization-and-multi-tenancy> Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Mar 30, 2017, at 12:08 PM, Nijandan D <[email protected]> wrote: > > Hi, > > Implemented SSL in Nifi source. After changing all properties, SSL enabled > successfully in nifi source. But when enter Url in browser, it shows > unauthorized error for few seconds and then it redirects to login url. > Attached screenshot below: > > <image.png> > > I checked Log file and found an error that shown below: > > <image.png> > Can I know in what case this error will reproduce? also how to fix this? > > Thanks in advance >
signature.asc
Description: Message signed with OpenPGP using GPGMail
