Using OAuth for web service security
The
OAuth
protocol became one of the dominant ways to perform authorization in the emerging amount of web applications and services. The final draft of v1.0 was released in 2007. In 2009, v1.0a was published to fix a security flaw known as session fixation.
In October 2012, OAuth 2.0 was released. It is not backward compatible with OAuth 1.0a. OAuth 2.0 received a lot of negative criticism, even though some of the major providers (such as Google or Facebook) support OAuth 2.0 already. Furthermore, the new protocol specification leaves too many open points to the implementer, which makes it somewhat hard to apply a generic approach to.
In this recipe, we will cover the OAuth 1.0a protocol and how it can be used to authorize your access to the Twitter API.
Getting ready
The scenario that we will try to achieve is a standalone application that reads tweets on a user's behalf:
First of all, you need to register your application (script) with Twitter through this...