<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008G7UmNSAVOkta Classic EngineSingle Sign-OnAnswered2024-04-29T20:16:18.000Z2017-12-27T00:17:54.000Z2017-12-27T00:17:54.000Z

AmberH.81592 (Customer) asked a question.

Why does the option in a SWA application of "Users share a single username and password set by administrator" still appear to be logging the users in with their "personal/work" Google account?
Why does the option in a SWA application of "Users share a single username and password set by administrator" still appear to be logging the users in with their "personal/work" Google account?

  • If the user has previously signed into GSuite and not signed out, their old session may still be valid.  That is to say, when they click on the chicklet, the creds are not taken and the existing personal/work session is used.
  • AmberH.81592 (Customer)

    Hi James, 

     

    This is kind of what I was figuring. The problem we have is that we are setup with Desktop SSO at our company. So it seems that there is no way around this as we are all always logged into our Google Company accounts. What happens is even if the user tries to sign out we are automatically signed back in. 

     

    Any other suggestions or possible work arounds for this? We have several SWA apps and this is starting to become a bigger issue.
    Expand Post
This question is closed.
Loading
Why does the option in a SWA application of "Users share a single username and password set by administrator" still appear to be logging the users in with their "personal/work" Google account?