Logout issue in external identity (Okta)

MUHAMMED SHAQUIQ 21 Reputation points

I have added Okta as an External Identity using SAML in my mobile application(Android). This is all working but, when I try to logout a guest user, the user will logout from the azure but the Okta session of that user is still active. So, when I try to login with another guest user Okta will automatically returns the previous one. Is there any way to clear the okta session?

Thanks in advance for any help or suggestions.


Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,458 questions
0 comments No comments
{count} votes

Accepted answer
  1. JamesTran-MSFT 36,531 Reputation points Microsoft Employee

    Thank you for your post! I'll share a summary below so I can gain a better understanding of your issue.

    Within your Android application, you added Okta as an External Identity using SAML, and everything is working as intended.

    When trying to log out a Guest user, the user will be logged out of Azure, but their Okta session will continue to remain active. As a result, Okta always provides the previous guest user when logging in with another user.


    As mentioned by @Dillon Silzer , because your Okta session won't log the user(s) out, I'd recommend reaching out to the Okta Support Team to see if their engineers and community can take a closer look into your issue. Additionally, I'd recommend making sure you followed the Okta documentation fully when implementing the Sign Out behavior, to make sure you didn't miss anything.

    Additional Links:
    Create an Okta support case
    Okta Community
    Okta Classic Engine - Sign users out
    Okta Identity Engine - User sign out (local app)
    Okta - Configure Single Logout in app integrations

    I hope this helps!

    If you have any other questions, please let me know.
    Thank you for your time and patience throughout this issue.


    Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

1 additional answer

Sort by: Most helpful
  1. Dillon Silzer 56,036 Reputation points


    This sounds more of an Okta-end issue as Azure is doing its job by logging out the user.

    I'd recommend opening a case with Okta:


    This Okta documentation may help as well:



    If this is helpful please accept answer.