Ryan, I haven't had time to look into your other email yet, but I can confirm that Kerberos is not required for a secure cluster, and you always end up seeing that 409 conflict for access/kerberos.
Thanks, Bryan On Thu, Mar 16, 2017 at 12:41 PM, Ryan H <[email protected]> wrote: > As a follow up to the last email, when looking at the Chrome Dev Tools, > there are two requests that are failing when trying to access the UI. > > This Request Succeeds: > > Request URL: > https://my-server-address/nifi/ > Request Method: > GET > Status Code: > 200 OK > Remote Address: > 10.227.80.39:443 > Referrer Policy: > no-referrer-when-downgrade > > > Then These Fail: > > Request URL: > https://my-server-address/nifi-api/access/kerberos > Request Method: > POST > Status Code: > 409 Conflict > Remote Address: > 10.227.80.39:443 > Referrer Policy: > no-referrer-when-downgrade > > Request URL: > https://my-server-address/nifi-api/flow/current-user > Request Method: > GET > Status Code: > 500 Internal Server Error > Remote Address: > 10.227.80.39:443 > Referrer Policy: > no-referrer-when-downgrade > > > > Cheers, > > Ryan H. > > On Thu, Mar 16, 2017 at 11:52 AM, Ryan H <[email protected]> > wrote: >> >> Hi All, >> >> In response to the error that I posted about earlier today, I couldn't >> help but wonder if Kerberos is required when setting up a secure NiFi >> cluster. Is this the case? >> >> Error in reference when trying to access the UI for a 2 node secure >> cluster (version 1.1.1) in AWS: >> >> 2017-03-16 12:39:41,110 INFO [NiFi Web Server-117] >> o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: >> Kerberos ticket login not supported by this NiFi.. Returning Conflict >> response. >> >> Any thoughts on this? Or is this possibly a misleading error shown in the >> nifi-user.log... >> >> >> -Ryan H. > >
