While oauth/authenticate with force_login=true does force users to provide credentials, oauth/authenticate leaves them logged into twitter, which is somewhat dangerous from a shared or public computer.
oauth/authorize used to behave differently - it didn't leave users logged in. However, that changed - see http://code.google.com/p/twitter-api/issues/detail?id=1453 . On Apr 20, 5:55 pm, Abraham Williams <4bra...@gmail.com> wrote: > You can add send users > tohttps://twitter.com/oauth/authenticate?oauth_token=xyz&force_login=tr... > the &force_login=true) to have users always prompted for username > and password on twitter.com. > > http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate > > <http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate> > Abraham > > > > > > On Tue, Apr 20, 2010 at 12:48, Jonathon Hill <jhill9...@gmail.com> wrote: > > Hello, > > > I'm building an app that uses OAuth for registration and > > authentication. Is there any way to log an authenticated user out of > > twitter, so that he/she can log in with a different twitter account? > > > Calling the REST endpoint /account/end_session.json doesn't work. > > > Thanks, > > > Jonathon Hill > > > Company52 > >http://company52.com > > @compwright > > > -- > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > > -- > Abraham Williams | Developer for hire |http://abrah.am > PoseurTech Labs | Projects |http://labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private.- Hide quoted text - > > - Show quoted text -
