I'm facing the same issue on all my Nifi instances with different versions (1.18.0, 1.19.1) on Windows, though on MAC I don't have this issue. I believe it's a Windows issue. Where there any leads from your side @myuintelli2021? ... View more

@myuintelli2021  Hello Ming, NiFi 1.15.3 will support JDK 1.8 or 1.11.  We do strongly encourage users to be on the latest update version of either of those with NiFI.  So not sure what update release of JDK your are on and which JDK provider (Oracle, OpenJDK, etc) you are using. I unfortunately do not have access ti a Windows 2019 datacenter edition to  see if I can reproduce myself to evaluate further. I strongly encourage you to raise a community question to take your query further.  A new question will gather more attention rather than trying to diagnosis and resolve your specific issue with the comments of a community article. Thank you, Matt ... View more

By checking the status of https://issues.apache.org/jira/browse/NIFIREG-313, it seems that the feature of authenticating using OIDC for nifi registry is already resolved as of 9/14/2020. But In nifi registry admin guide at https://nifi.apache.org/docs/nifi-registry-docs/index.html, it still mentions that only LDAP and Kerberos are supported. Is the document up-to-date? ... View more

@myuintelli2021 ,   Good point! I hadn't noticed that.   Alternatively, you can download the NiFi Toolkit and use the encrypt-config.bat to perform the key migration.    Check this out: https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#sensitive-property-key-migration   The toolkit contains a Windows version of the script (encrypt-config.bat).   HTH, André   ... View more

@VidyaSargur We have not resolved the issue yet due to some priority shift. We're still seeing the same error. Will follow up on it soon. Ming ... View more

@myuintelli2021  Assisting on your new post here: https://community.cloudera.com/t5/Support-Questions/Nifi-untrusted-proxy-caused-by-Untrusted-Proxy-Exception/m-p/317796/highlight/false#M227327 Your choice of user authentication does not matter here.  Authentication and Authorization processes are handled independently of one another.  The Authentication of users/clients results in a string which is evaluated against identity mapping properties and then passed to the configured authorizer for authorization. Your exception points and missing /proxy authorization for your node strings. Hope this helps, Matt ... View more