Hi Guys We've also noticed the UX for the current OAuth flow isn't great: the account that you're authorising (initially) isn't so clear. Currently it's just the username in bold text, amid a paragraph of blurb. Compared with @Anywhere, where the avatar is shown, this kinda stinks :-)
In Socialite[1], to counteract user confusion we now make sure that users are clear with which account they're signing in with by appending &force_login=true [2] to each https://twitter.com/oauth/authenticate/ request we start the OAuth side of things. Cheers -N -- Nik Fletcher @nikf [1] http://www.realmacsoftware.com/socialite [2] e.g. https://twitter.com/oauth/authenticate/?oauth_token=<snip>&force_login=true On Aug 23, 10:23 am, Varun Jain <friends.made....@gmail.com> wrote: > Hey Twitter Support, > > That's the same problem i'm running into too. If I use the url oauth/ > authenticate, it serves my purpose, but if I use oauth/authorize, > it's failing under the multiple login. > > can anyone give me a solution to this. > > Thanks, > Varun Jain > > On Aug 6, 9:41 pm, Nick Spacek <nick.spa...@gmail.com> wrote: > > > > > That's a long subject line, but I haven't seen much related to it > > (there was one post last Autumn but didn't seem to have any > > resolutions. > > > I'm working on an app where an app user may want to authorize multiple > > Twitter accounts. Right now if they are already logged into Twitter > > (say, with their primary account) and the account is already > > authorized, they don't even get the option to sign in to a different > > account; the OAuth flow just redirects the browser immediately to the > > callback URL. Is there any way around this? > > > Is there some way to pass a username on the GET or in the headers? > > > Thanks, > > Nick
