You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:07 UTC

[jira] [Resolved] (NIFI-5493) Reverse Proxy & OIDC

     [ https://issues.apache.org/jira/browse/NIFI-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-5493.
----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> Reverse Proxy & OIDC
> --------------------
>
>                 Key: NIFI-5493
>                 URL: https://issues.apache.org/jira/browse/NIFI-5493
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 1.7.0, 1.7.1
>         Environment: Reverse Proxy w/ SSL Client Auth between Nifi and Reverse Proxy
>            Reporter: Curtis W Ruck
>            Priority: Major
>
> In my environment we have a reverse proxy that (httpd) that does SSL Client Auth to authenticate the TLS session between reverse proxy and application servers.
> When trying to configure OIDC authentication, the reverse proxy's SSL Client Auth certificate is "authenticated" prior to triggering the OIDC redirect for authentication.
> Ideally, I believe there should be a mechanism to disable NiFi Client Auth, or enabling a priority between authentication mechanisms.



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