Difference between revisions of "Mistral/Blueprints/OAuth"
< Mistral | Blueprints
(→Mistral OAuth support) |
(→Mistral OAuth support) |
||
Line 2: | Line 2: | ||
'''OAuth''' is an open standard for authorization. '''OAuth''' provides client applications a 'secure delegated access' to server resources on behalf of a resource owner. It specifies a process for resource owners to authorize third-party access to their server resources without sharing their credentials. Designed specifically to work with HTTP, '''OAuth''' essentially allows access tokens to be issued to third-party clients by an authorization server, with the approval of the resource owner, or end-user. The client then uses the access token to access the protected resources hosted by the resource server. | '''OAuth''' is an open standard for authorization. '''OAuth''' provides client applications a 'secure delegated access' to server resources on behalf of a resource owner. It specifies a process for resource owners to authorize third-party access to their server resources without sharing their credentials. Designed specifically to work with HTTP, '''OAuth''' essentially allows access tokens to be issued to third-party clients by an authorization server, with the approval of the resource owner, or end-user. The client then uses the access token to access the protected resources hosted by the resource server. | ||
− | [[File:Mistral OAuth.png| | + | [[File:Mistral OAuth.png|500px|framed|center|Mistral OAuth]] |
Revision as of 13:54, 30 May 2014
Mistral OAuth support
OAuth is an open standard for authorization. OAuth provides client applications a 'secure delegated access' to server resources on behalf of a resource owner. It specifies a process for resource owners to authorize third-party access to their server resources without sharing their credentials. Designed specifically to work with HTTP, OAuth essentially allows access tokens to be issued to third-party clients by an authorization server, with the approval of the resource owner, or end-user. The client then uses the access token to access the protected resources hosted by the resource server.