OpenID Connect: Difference between revisions
m categorization/tagging using AWB |
Timtempleton (talk | contribs) Clarified definition to improve article |
||
Line 3: | Line 3: | ||
==Description== |
==Description== |
||
OpenID Connect is a simple identity layer on top of the [[OAuth]] 2.0 protocol, which allows [[Client (computing)| computing clients]] to verify the identity of an end-user based on the authentication performed by an authorization server, as well as to obtain basic profile information about the end-user in an interoperable and [[REST]]-like manner. The term REST-like manner indicates that the software architectural style within the distributed [[hypermedia]] system adheres to a coordinated set of architectural constraints applied to the components, connectors, and data elements. In technical terms, OpenID Connect specifies a [[RESTful]] [[HTTP]] [[API]], using [[JSON]] as a data format. |
|||
OpenID Connect specifies a [[RESTful]] [[HTTP]] [[API]], using [[JSON]] as a data format. |
|||
OpenID Connect allows a range of clients, including Web-based, mobile, and [[JavaScript]] clients, to request and receive information about authenticated sessions and end-users. The specification suite is [[Extensibility|extensible]], supporting optional features such as encryption of identity data, discovery of OpenID Providers, and session management.<ref>{{cite web|url=http://openid.net/connect/ |title=Welcome to OpenID Connect|publisher=OpenID.net |accessdate=2013-05-28}}</ref> |
|||
==Adoption== |
==Adoption== |
Revision as of 16:48, 17 May 2014
OpenID Connect is an authentication layer on top of OAuth 2.0, an authorization framework.[1] The standard is controlled by the OpenID Foundation.
Description
OpenID Connect is a simple identity layer on top of the OAuth 2.0 protocol, which allows computing clients to verify the identity of an end-user based on the authentication performed by an authorization server, as well as to obtain basic profile information about the end-user in an interoperable and REST-like manner. The term REST-like manner indicates that the software architectural style within the distributed hypermedia system adheres to a coordinated set of architectural constraints applied to the components, connectors, and data elements. In technical terms, OpenID Connect specifies a RESTful HTTP API, using JSON as a data format.
OpenID Connect allows a range of clients, including Web-based, mobile, and JavaScript clients, to request and receive information about authenticated sessions and end-users. The specification suite is extensible, supporting optional features such as encryption of identity data, discovery of OpenID Providers, and session management.[2]
Adoption
Companies that have started to use OpenID Connect include Google, Microsoft, Deutsche Telekom, salesforce.com, and the Nomura Research Institute.[3]
See also
References
- ^ "OpenID Connect".
- ^ "Welcome to OpenID Connect". OpenID.net. Retrieved 2013-05-28.
- ^ "The OpenID Foundation Launches the OpenID Connect Standard".
External links
This redirect has not been added to any content categories. Please help out by adding categories to it so that it can be listed with similar redirects, in addition to a stub category. (May 2014) |