Overview#
Userinfo_endpoint in OpenID Connect is an Endpoint that provides a standardized REST API for Identity Attributes.Communication with the Userinfo_endpoint MUST utilize TLS. Section 16.17 for more information on using TLS.
The Userinfo_endpoint MUST support the use of the HTTP GET and HTTP POST methods defined in RFC 2616.
The Userinfo_endpoint MUST accept Access Tokens as OAuth 2.0 Bearer Token Usage RFC 6750.
The Userinfo_endpoint SHOULD support the use of Cross Origin Resource Sharing (CORS) and or other methods as appropriate to enable Java Script Clients to access the endpoint.
Userinfo_endpoint #
- UserInfo Request - HTTP GET or HTTP POST using an Access Token obtained through OpenID Connect Authentication Request.
- UserInfo Response - A JSON Object
More Information#
There might be more information for this subject on one of the following:- API-Gateway
- Acr
- Apple ID
- Authentication Context Class Reference
- Authorization Code Flow
- Authorization Server Request End-User Consent-Authorization
- Default Profile Claims
- Identity Token
- Offline_access
- OpenAM Endpoints
- OpenID Connect
- OpenID Connect Authentication Response
- OpenID Connect Claims
- OpenID Connect Endpoints
- OpenID Connect Profile for SCIM Services
- OpenID Connect Scopes
- OpenID Connect Standard Claims
- OpenID Connect Use Cases
- Openid-configuration
- OxAuth
- Profile
- Self-Issued OpenID Provider
- Smart-On-FHIR profile
- UserInfo Request
- UserInfo Response
- Userinfo_encryption_alg_values_supported
- Userinfo_encryption_enc_values_supported
- Userinfo_signing_alg_values_supported
- Web Blog_blogentry_300717_1
- [#1] - UserInfo Endpoint
- based on data observed:2015-06-11