cloudfoundry / cloudfoundry/uaa
RP initiative logout is not working in case of SAML
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 844
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 27
Description
UAA Version : 77.10.0
As per my configuration, the identity zone “octopus” is configured with Auth0 as a SAML Identity Provider.
The Auth0 SAML metadata configured in the octopus identity zone includes a valid SingleLogoutService endpoint.
As per our configuration, the identity zone “octopus” is configured with Auth0 as a SAML Identity Provider.
The Auth0 SAML metadata configured in the octopus identity zone includes a valid SingleLogoutService endpoint.
Current Behavior
When the user accesses this url from the browser https://octopus.<uaa_domain>/logout.do
the following occurs:
- CF UAA clears the local session cookies.
- The user is redirected to: https://octopus.<uaa_domain>/login
- /login immediately initiates a new SAML authentication request to Auth0.
Problem
CF UAA does not trigger a SAML Single Logout (SLO) request to Auth0
Even though the IdP metadata contains a SingleLogoutService endpoint, no SAML LogoutRequest is sent to Auth0 during /logout.do.
As a result:
The session at Auth0 remains active.
The user is immediately re-authenticated due to the existing IdP session.
Proper federated logout does not occur.
Could you please clarify:
Whether additional configuration is required to enable SAML SLO from UAA to the external IdP?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /logout.do and /login entry points and trace how a SAML identity provider's SingleLogoutService metadata is handled. Reproduce the flow with the octopus identity zone and Auth0 configuration described in the issue, then verify whether a SAML LogoutRequest is sent and whether the session is no longer immediately re-authenticated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100