OAuth Core 1.0

OAuth Core 1.0

Abstract

The OAuth protocol enables websites or applications (Consumers) to access Protected Resources from a web service (Service Provider) via an API, without requiring Users to disclose their Service Provider credentials to the Consumers. More generally, OAuth creates a freely-implementable and generic methodology for API authentication.

An example use case is allowing printing service printer.example.com (the Consumer), to access private photos stored on photos.example.net (the Service Provider) without requiring Users to provide their photos.example.net credentials to printer.example.com.

OAuth does not require a specific user interface or interaction pattern, nor does it specify how Service Providers authenticate Users, making the protocol ideally suited for cases where authentication credentials are unavailable to the Consumer, such as with OpenID.

OAuth aims to unify the experience and implementation of delegated web service authentication into a single, community-driven protocol. OAuth builds on existing protocols and best practices that have been independently implemented by various websites. An open standard, supported by large and small providers alike, promotes a consistent and trusted experience for both application developers and the users of those applications.

License

This specification is made available under the OAuth Non-Assertion Covenant and Author’s Contribution License For OAuth Specification 1.0 available at http://oauth.net/license/core/1.0. Copyrights are licensed under the terms of the Creative Commons Attribution –ShareAlike 3.0 license available at http://creativecommons.org/licenses/by-sa/3.0.

More information visit here

http://oauth.net/core/1.0/