You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2024/05/25 20:19:00 UTC

[jira] [Commented] (NIFI-13295) Remove Apache Knox SSO Integration

    [ https://issues.apache.org/jira/browse/NIFI-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849488#comment-17849488 ] 

ASF subversion and git services commented on NIFI-13295:
--------------------------------------------------------

Commit fa8dc4f1a0c56bcb3c006defef52775d9fb9db71 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fa8dc4f1a0 ]

NIFI-13295 Removed Apache Knox SSO Authentication
This closes #8876

Signed-off-by: Joseph Witt <jo...@apache.org>


> Remove Apache Knox SSO Integration
> ----------------------------------
>
>                 Key: NIFI-13295
>                 URL: https://issues.apache.org/jira/browse/NIFI-13295
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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|https://knox.apache.org/books/knox-1-6-0/user-guide.html#Nifi+UI] 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)