You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Patrick
0a63a7466b
|
12 years ago | |
---|---|---|
.. | ||
Architecture.txt | 12 years ago | |
OAuth2.0_Diagrams.pdf | 13 years ago | |
OpenID_Connect_Diagrams.pdf | 13 years ago | |
UserApproval.png | 12 years ago | |
architectureDiagram.png | 13 years ago | |
readme.txt | 13 years ago |
readme.txt
Changelog
Updated on 3/6/2012
Connect:
* "Authorization Code Flow" diagram: changed step B to be a redirect rather than a JSON response object.
Updated on 2/21/2012
OAuth2:
* Renamed "Access Code Flow" to "Authorization Code Flow".
* Changed all references to "User" to "Resource Owner".
* Changed final "Response"s to "JSON respones object"s.
* Added initial "Authenticate Resource Owner" step to Authorization Code Flow
Connect:
* Changed final "Response"s to "JSON respones object"s.
Updated on 2/7/2012
OAuth2:
* Removed refresh_token from the Access Token response on the Client Credentials flow.
Ref: http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-4.4.3
"A refresh token SHOULD NOT be included."
* Changed "Consumer" to "Client".
Connect:
* Changed "Consumer" to "Client".
* Clarified required/optional wording. Parameters are REQUIRED unless otherwise stated.
* Implicit Flow: changed wording on redirect_uri requirement in the Authorization Request. Now reads "required IFF the client has pre-configured more than one value with the service provider".
* Diagram 3 was renamed to "Optional Steps" (from "Additional Steps"), as these steps may or may not be taken and may be done in any order. Added "openid" to the schema parameter in the UserInfo Request.