Thanks for the quick response. A couple of things I am seeing.
1. There is no error, I don’t see anything in the logs once the service comes up. This is because the health check is not even hitting the instance when secure. 2. Nothing interesting in the nifi-registry-app.logs. That was my concern because on my nifi instance I can see the health check hitting the instance from the ELB. This does not happen on the nifi-registry instance. I see the service startup and it tells me what domain and port I can access the UI but nothing else after that. 3. When I am on an instances in the same private subnet I am able to curl to the instance I get the TLS SSL which tells me the keystore is on the server. I am using a JKS keystore that is self-signed by the company I work for. > On Mar 19, 2018, at 9:10 AM, Bryan Bende <[email protected]> wrote: > > Hello, > > What error are you getting when you cannot access the UI? > > Is there anything interesting in nifi-registry-app.log regarding > authentication/authorization when this happens? > > Can you access the UI securely without going through the ELB? > > Thanks, > > Bryan > > > On Mon, Mar 19, 2018 at 10:05 AM, Scott Howell <[email protected]> > wrote: >> I was able to stand up nifi-registry behind an AWS ELB non-secure. >> Everything was working great and was able to access the UI anonymously. I >> set up the authorization just like on my nifi instances along with the >> authorizers and identity-provider. The service comes up without errors and >> everything looks good but the health check does not pass and I cannot access >> the UI to login. I was wondering if anyone else has ran into this issue >> using nifi-registry.
