How to fix the following SAML SSO issue when logging out of 3rd party application. Error code: AADSTS50068: Signout failed. The initiating application is not a participant in the current session.

Question

How to fix the following SAML SSO issue when logging out of 3rd party application. Error code: AADSTS50068: Signout failed. The initiating application is not a participant in the current session.

Gary Curtis 0

We are using a service desk application called ServiceDesk Plus MSP. We have created an enterprise application to use SAML SSO for logging into the application. We are getting the below error when trying to logout of the application. After trying to find a resolution we are still facing the issue. User's image

Sami Wahedi 5 Reputation points

2023-04-14T14:29:40.1266667+00:00

I have the same problem.
Shweta Mathur 30,471 Reputation points Microsoft Employee Moderator

2023-04-25T10:53:17.3+00:00

@Gary Curtis ,

Thanks for reaching out.

This would require HTTP trace debugging (such as Fiddler tool) to see what's being called when you click on logout on your WebApp (error: "AADSTS50068: Signout failed ) because it supposed to trigger a HTTP redirect logout call to https://login.windows.net/{tenantid or "common"}/oauth2/logout?post_logout_redirect_uri={URL} ( The URL needs to be a reply url registered with your application in Azure AD) also this would help us validating whether application is clearing the user's session data successfully.

Thanks,

Shweta
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Shikh Ahmad, Danya 0 Reputation points

2024-10-25T18:10:07.28+00:00

nop i can song in why
Anonymous

2025-10-27T14:10:14.2566667+00:00

What is the solution to this issue? we also face the same.

Your answer

Sami Wahedi 5 Reputation points

2023-04-14T14:29:40.1266667+00:00

I have the same problem.
Shweta Mathur 30,471 Reputation points Microsoft Employee Moderator

2023-04-25T10:53:17.3+00:00

@Gary Curtis ,

Thanks for reaching out.

This would require HTTP trace debugging (such as Fiddler tool) to see what's being called when you click on logout on your WebApp (error: "AADSTS50068: Signout failed ) because it supposed to trigger a HTTP redirect logout call to https://login.windows.net/{tenantid or "common"}/oauth2/logout?post_logout_redirect_uri={URL} ( The URL needs to be a reply url registered with your application in Azure AD) also this would help us validating whether application is clearing the user's session data successfully.

Thanks,

Shweta
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Shikh Ahmad, Danya 0 Reputation points

2024-10-25T18:10:07.28+00:00

nop i can song in why
Anonymous

2025-10-27T14:10:14.2566667+00:00

What is the solution to this issue? we also face the same.