This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 27 lines
!!! Overview
[{$pagename}] provides the client with the information required to successfully utilize the access token to make a protected resource request (along with type-specific attributes). The [OAuth Client] __MUST NOT__ use an [Access Token] if it does not understand the [{$pagename}].
For example, the [Bearer Token] type defined in [RFC 6750] is utilized by simply including the access token string in the request:[1]
{{{
GET /resource/1 HTTP/1.1
Host: example.com
Authorization: Bearer mF_9.B5f-4.1JqM
}}}
while the "mac" token type defined in [OAuth-HTTP-MAC] is utilized by issuing a [Message Authentication Code] (MAC) key together with the access token that is used to sign certain components of the HTTP requests:[1]
{{{
GET /resource/1 HTTP/1.1
Host: example.com
Authorization: MAC id="h480djs93hd8",
nonce="274312:dj83hs9s",
mac="kDZvddkndxvhGRXZhvuDjEWhGeE="
}}}
The above examples are provided for illustration purposes only.
Developers are advised to consult the [RFC 6750] and [OAuth-HTTP-MAC] specifications before use.
Each [{$pagename}] definition specifies the additional attributes (if any) sent to the [OAuth Client] together with the "access_token" response parameter. It also defines the HTTP authentication method used to include the [Access Token] when making a protected resource request.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [The OAuth 2.0 Authorization Framework-section-7.1|https://tools.ietf.org/html/rfc6749#section-7.1|target='_blank'] - based on information obtained 2013-04-10