<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
0D50Z00008C3jqJSAROkta Classic EngineOkta Integration NetworkAnswered2024-04-30T09:18:25.000Z2016-03-17T14:00:46.000Z2017-06-29T08:23:42.000Z
Twitter App does not sign into Twitter if already signed in
My organization has 12 Twitter accounts.  We have a separate Twitter app added for each Twitter account.  Each app is configured to use secure web authentication (SWA) which is the only sign-on option avaiable for Twitter.  The problem our users are having is, if I'm already logged into Twitter Account A, and I click on the Twitter Account B icon, I get taken to Twitter and I'm still logged into Twitter Account A -- not Account B.

 

It appears the reason is because when the browser reaches /login, Twitter issues a 302 redirect to https://twitter.com/ if it sees you are already logged in, and the Okta SWA Plug-In never gets a chance to enter the credentials for Twitter Account B.  The only way we are able to log into a different twitter account is if we explicitly log out of Twitter first, then go back to Okta, and click on the Twitter Okta app we're interested in logging in under.  This is confusing to most users, and the a hassle to the users that do understand he process.

 

Is there not another method available.  Some possible ideas I'm wondering if are available: 
  1. ​Could Okta first redirect to a Twitter logout URL and then redirect to /login?
  2. Is there a login page with a different URL that would allow the Okta SWA Plug-In to fill in the credentials without Twitter redirecting first?
  3. Could the Okta SWA Plug-In clear the Twitter cookie in the browser before redirecting.
 Any of these possible, or something else not listed above?

 

Thanks.

This question is closed.
Loading
Twitter App does not sign into Twitter if already signed in