Oauth - Role

Card Puncher Data Processing

Oauth - Role

About

OAuth defines four roles:

The interaction between this roles is described in the flow.

Example

An end-user (resource owner) can grant a printing service (client) access to her protected photos stored at a photo-sharing service (resource server), without sharing her username and password with the printing service.

Instead, she authenticates directly with a server trusted by the photo-sharing service (authorization server), which issues the printing service delegation-specific credentials (access token).

Documentation / Reference





Recommended Pages
Card Puncher Data Processing
Oauth - Authorization Server

Authorization Server in Oauth is one of the 4 oauth role. The server issuing access tokens to the client after successfully authenticating the resource owner and obtaining authorization. The authorization...
Card Puncher Data Processing
Oauth - Client (App)

client is one of the 4 roles of the Oauth specification. In its most basic form, it's a web site used by a end-user. In more details, it's is a (first-party or third party service application making...
Card Puncher Data Processing
Oauth - Flow (Abstract Protocol Flow)

The abstract OAuth 2.0 flow describes the interaction between the four roles. For each type of grant, you got a flow: Authorization Code Resource Owner Password Credentials Implicit Client...
Card Puncher Data Processing
Oauth - Resource Owner (End-User)

Oauth - Resource Owner (End-User) Resource owner is a role in Oauth. It's an entity capable of granting access to a protected resource. When the resource owner is a person, it is referred to as an...
Card Puncher Data Processing
Oauth - Resource Server

A resource server is one of the 4 roles of Oauth. It hosts the protected resources, capable of accepting and responding to protected resource requests using access tokens. An end-user (resource owner)...
Card Puncher Data Processing
Oauth 2.0 - Authorization framework

This section talks OAuth 2.0. (OAuth 2.0 replaces OAuth 1.0) The following two specifications provide a general framework for third-party applications (know as the client) to obtain and use limited...



Share this page:
Follow us:
Task Runner