Abstract. 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. Guide showing you how to use OpenID Connect 1.0 with ForgeRock® Access Management (AM). ForgeRock Access Management provides intelligent authentication, authorization, federation, and single sign-on functionality. Hi there! I'm one of the devs who worked on this feature (ID token in jobs) so I can shed some light on this. userinfo endpoint is an OAuth 2.0 Protected Resource and the client should send the Access Token as Bearer Token in the header.. Our current implementation of OIDC only supports ID Token response type (as shown in the discovery document). In this white paper, we show you how cloud-based identity management helps IT leaders overcome these challenges. Take low-adopter apps and turn them into business generators. Make systems that were once security liabilities function as your first line of defense against intrusions and breaches. Okta customers, such as Adobe, Zuora, and Rotary. In the Identity provider URL section, enter the IdP's OIDC well-known configuration endpoint. For Application ID, enter the ID of the OIDC app you created earlier. You will not be able to save the Passport library item without entering an identity provider URL and application ID.