1. Setup Nifi 1.11.4 secure using my own certs and kerberos authentication accepting username/password. All is working fine can log in using kerberos username/password as initial admin user. 2. Setup Nifi Registry 0.6.0 using same certs and kerberos all is fine. Again all is working fine can log in using kerberos username/password as initial admin user. Problem is that when adding registry to secure Nifi it seems they attempt to talk using the username 'anonymous'. If I add the user "anonymous" to Registry giving it permissions to proxy, then all works fine, however registry shows all changes were performed by 'anonymous' Also can't use policies to not allow the anonymous user access to the UI I can't find any documentation on why I would need to create a user with name 'anonymous' In fact most documentation says when using https that anonymous access it not supported. Q. How does Nifi/Registry identify the identity of the host in standalone mode? If I generate certs with tls-toolkit.sh it all works fine - but uses the identity I put in the cert. So I assume the problem is with getting this identity from my cert - but I don't see any errors just the name 'anonymous'? Any help appreciated Thanks John
... View more
