Federated Logout with Google SSO Retains Session

[ranchuk]

I’m using Auth0 with a SAML (SSO) connection configured for Google Workspace in my Next.js application. While logging in and out works generally well, I’m encountering an issue where logging out of Auth0 does not fully terminate the session with Google.

Here’s the scenario:

1. A user logs in with user1@domain.com via Google SSO.
2. The user logs out using the federated parameter in the Auth0 logout URL (/v2/logout?federated).
3. When attempting to log in with user2@domain.com, Google automatically logs in user1@domain.com without prompting for new credentials.

I’ve already:

• Ensured prompt: 'login' is included in the login flow.
• Configured the federated parameter in the logout URL.
• Tested manually visiting https://accounts.google.com/Logout, which resolves the issue, but I need this behavior integrated automatically.

Despite these efforts, Google’s session remains active after logging out of Auth0. Is there a configuration or additional step required to ensure that federated logout properly terminates the Google session? Any insights or guidance would be appreciated!

[sumansaurav]

Hi @ranchuk ,

You can look at this article and get an idea how to handle this scenario.

Issue with Google Workspace SSO Using SAML with Only One Active Session

Problem statement With a Google Workspace as the SAML IdP, and an active Google session that is not part of the SAML connection, it returns the error Application is not setup for the user instead of allowing the user to login to a different user. Steps to reproduce The user has one active session on Google, as e.g. john.doe@somedomain.com The user logs in example platform as foobar@example.com Auth0 sees that @example.com domain corresponds to the Google Workspace SAML connection so it redirec…

I would suggest you to implement custom logout handler that manages Google and Auth0 sessions

Let me know if this doesn’t work.