Troubleshooting: RP-Initiated Logout Shows a Consent Prompt in SecureAuth Connect

Version Affected: SecureAuth Connect
 
 

Overview

Sending an RP-Initiated logout request in SecureAuth Connect (for example, to https://<tenant>.<region>.connect.secureauth.com/<tenant>/<workspace>/oidc/logout?id_token_hint=id_token_issued_to_client&post_logout_redirect_uri=https://client.com/logged_out) shows the user a logout consent prompt.

Cause

This is by design.

Resolution:

To skip the logout consent prompt, configure the application to use the non-OIDC logout endpoint instead, with id_token_hint and redirect_to query parameters:

https://<tenant>.<region>.connect.secureauth.com/<tenant>/<workspace>/logout?id_token_hint={token}&redirect_to=&post_logout_redirect_uri=https%3A%2F%2Fexample.com

Special Considerations

See SecureAuth's OIDC Single Logout documentation for more detail.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.