Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
As described in NIFI-13294, custom Single Sign-On integration with Apache Knox based on JSON Web Tokens and custom public key verification should be removed from the main branch. Proxy access through Apache Knox should remain supported through the non-product-specific X-ProxiedEntitiesChain HTTP header strategy with X.509 client certificates.
OpenID Connect and SAML 2 integration continue to provide standards-based Single Sign-On solutions, obviating the need for custom cookie-based token communication and verification.
Attachments
Issue Links
- links to
- mentioned in
-
Page Loading...