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: 1. Request URL: https://my-server-address/nifi/ 2. Request Method: GET 3. Status Code: 200 OK 4. Remote Address: 10.227.80.39:443 5. Referrer Policy: no-referrer-when-downgrade Then These Fail: 1. Request URL: https://my-server-address/nifi-api/access/kerberos 2. Request Method: POST 3. Status Code: 409 Conflict 4. Remote Address: 10.227.80.39:443 5. Referrer Policy: no-referrer-when-downgrade 1. Request URL: https://my-server-address/nifi-api/flow/current-user 2. Request Method: GET 3. Status Code: 500 Internal Server Error 4. Remote Address: 10.227.80.39:443 5. 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. >
