Setting a New Web-Standard with OAuth for Secure API Authentication
Current trends in information architecture, the development of user-provided information and the use and combination of single function focused applications show that the Internet is shifting to a medium that is more and more structured with a decentralized authority.
Instead of using a single site for all online needs users use different sites and services to manage their online experience applying state of the art Data APIs allowing aplications to access their data. Making use of a Web-standard like
OAuth for secure API authentication gives your users access to their data while protecting their passwords and other protected areas. From
OAuth:
"Many luxury cars today come with a valet key. It is a special key you give the parking attendant and unlike your regular key, will not allow the car to drive more than a mile or two. Some valet keys will not open the trunk, while others will block access to your onboard cell phone address book. Regardless of what restrictions the valet key imposes, the idea is very clever. You give someone limited access to your car with a special key, while using your regular key to unlock everything."
Here is a short demo of what it means to end users:
While
reviewing one of the latest Google innovations,
Google App Engine, which lets one run Web applications on Google's infrastructure with no servers to maintain I found it worth to mention OAuth as an open standard for secure API authentication -
OAuth is now supported on all of the
Google Data APIs. Being familiar with UML or sequence diagrams it's easy to understand the Google data
API authentication process. More on
Google Data APIs blog.
Resources:
Labels: apis, bizdev, cloud, google, mashup, networking, oauth, security, strategy