OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines a mechanism for a Relying Party to request that an OpenID…
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines how an OpenID Connect Relying Party can dynamically register…
Information technology — OpenID connect — OpenID connect core 1.0 incorporating errata set 2
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines the core OpenID Connect functionality: authentication built on…
1 Scope
1.1 Inclusions
The requirements specified in this Standard apply to wall and ceiling-mounted track lighting systems intended to be installed in non-hazardous dry locations in accordance with the Canadian Electrical Code, Part I.
These requirements apply to
a)
permanently installed track systems
i)
rated 347 V or less, 40 A max;
ii)
supplied by a power source with an output of 30…
Information technology - OpenID connect - OpenID connect discovery 1.0 incorporating errata set 2
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines a mechanism for an OpenID Connect Relying Party to discover the…
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines a logout mechanism that uses direct back-channel communication…
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines how an OpenID Connect Relying Party can dynamically register…
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines a logout mechanism that uses front-channel communication via the…
Information technology - OpenID connect - OpenID connect core 1.0 incorporating errata set 2
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the 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.
This document defines the core OpenID Connect functionality: authentication built on…
Information technology - OpenID connect - OAuth 2.0 form post response mode
This document defines the Form Post Response Mode. In this mode, Authorization Response parameters are encoded as HTML form values that are auto-submitted in the User Agent, and thus are transmitted via the HTTP POST method to the Client, with the result parameters being encoded in the body using the application/x-www-form-urlencoded format.
