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

David Arreola updated NIFI-16258:
---------------------------------
    Description: 
NiFi hardcodes the post_logout_redirect_uri sent to the OIDC provider's 
end_session_endpoint to /nifi/logout-complete. This URI can be used to drive a 
custom logout flow before returning to NiFi. NiFi does not allow the URI to be 
configured, and always defaults to the host URL with the path 
/nifi/logout-complete. 

I'd like to add a new property that allows configuring the post-logout redirect 
URI. When the property is blank, it can fall back to the existing default.

  was:
NiFi hardcodes the post_logout_redirect_uri sent to the OIDC provider's 
end_session_endpoint to /nifi/logout-complete. This URI can be used to drive a 
custom logout flow before returning to NiFi. NiFi does not allow the URI to be 
configured, and always defaults to the host URL with the path 
/nifi/logout-complete.  

I'd like to add a new property that allows configuring the post-logout redirect 
URI. When the property is blank, it will fall back to the existing default.


> configurable OIDC post-logout redirect URI
> ------------------------------------------
>
>                 Key: NIFI-16258
>                 URL: https://issues.apache.org/jira/browse/NIFI-16258
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Security
>    Affects Versions: 2.0.0, 2.8.0
>            Reporter: David Arreola
>            Priority: Minor
>              Labels: SSO
>
> NiFi hardcodes the post_logout_redirect_uri sent to the OIDC provider's 
> end_session_endpoint to /nifi/logout-complete. This URI can be used to drive 
> a custom logout flow before returning to NiFi. NiFi does not allow the URI to 
> be configured, and always defaults to the host URL with the path 
> /nifi/logout-complete. 
> I'd like to add a new property that allows configuring the post-logout 
> redirect URI. When the property is blank, it can fall back to the existing 
> default.



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

Reply via email to