This worked well with basic authentication because you could just delegate the login to Twitter. Using OA
On Mar 21, 4:16 pm, Elliott Kember <[email protected]> wrote: > Hi Graeme, > > I think I'm doing a similar thing - I want to use Twitter as the > registration and login process for my app. Right now, Twitter asks for > approval every time the user logs into the account. Is there a way to > say "remember this application" and then always accept auth requests > from that application in future, like OpenID does? > > Long story short, I'm using OAuth like OpenID. Sorry to hijack your > thread, but I think we're after the same thing. > > Thanks, > Elliott > > On Mar 21, 11:35 am, GraemeF <[email protected]> wrote: > > > I have an application that does not need access to anything in or do > > anything to a Twitter account, it just wants proof that the user owns > > the account. This doesn't seen to fit with OAuth; the app needs proof > > of identity rather than authorization, so in fact OpenID would be more > > suitable than OAuth. > > > Ideally I would be able to get the username and user id from the > > Twitter API without getting authorization for anything else. What's > > the best way to tackle this? > > > Cheers, > > Graeme.
