Twitter'll phase out Basic HTTP Authentication by August 2010. In the link, my scripts are from desktop applications. Basically, my client should tweet new messages on the website.
That would be incredibly simple with the basic HTTP protocol, because I can store and use the username and password in the application for authentication. However, with OAUTH, I can get final authority in two ways:
- Callback method . You are redirected to Twitter, (login if is not), click "Allow access", redirect back to your callback URL.
- PIN mode . You get a link to open, (login if is not), click "Allow access", get a PIN code. Use this PIN to authenticate your application.
Do I understand correctly that the PIN is also expiring? How is this possible given the username and password only for tweets from the client application? How does the server side of the script log in with a username / password and allow access? All the scenarios I could run by Google is a web application to authenticate through , where the user is in front of the browser to go through the redirect.
source
share