Difference between revisions of "Authorization Code"
From MgmtWiki
(→Problems) |
(→Solutions) |
||
| Line 10: | Line 10: | ||
==Solutions== | ==Solutions== | ||
Based on the protocol selection of OpenID Connect, the full solution is described in the [[Identity Model]]. | Based on the protocol selection of OpenID Connect, the full solution is described in the [[Identity Model]]. | ||
| + | |||
| + | This is the definition in RFC 6749. | ||
| + | |||
| + | The authorization code is obtained by using an authorization server | ||
| + | as an intermediary between the client and resource owner. Instead of | ||
| + | requesting authorization directly from the resource owner, the client | ||
| + | directs the resource owner to an authorization server (via its | ||
| + | user-agent as defined in [RFC2616]), which in turn directs the | ||
| + | resource owner back to the client with the authorization code. | ||
Other protocols, like SAML are also available. | Other protocols, like SAML are also available. | ||
Revision as of 13:57, 8 July 2018
Full Title or Meme
Information passed from an Identifier or Attribute Provider to a Relying Party to indicate that the user has consented to authorized access to User Information.
Context
The context is an internet flow of Authorization as consented by the User.
Problems
Provide access to User Information in order to enable the user to obtain the access desired to some internet Resource.
Solutions
Based on the protocol selection of OpenID Connect, the full solution is described in the Identity Model.
This is the definition in RFC 6749.
The authorization code is obtained by using an authorization server as an intermediary between the client and resource owner. Instead of requesting authorization directly from the resource owner, the client directs the resource owner to an authorization server (via its user-agent as defined in [RFC2616]), which in turn directs the resource owner back to the client with the authorization code.
Other protocols, like SAML are also available.
