Connecting OIDC-compliant IDP

Instructions on how to connect an OIDC-compliant Identity Provider to Authorization Control Plane.

About the OIDC connector

OIDC is an interoperable authentication protocol based on the OAuth 2.0 family of specifications. All OIDC-compliant Identity Providers can be connected to ACP for user authentication purposes, in accordance with the Bring Your Own Identity philosophy that ACP follows. For more information about OIDC itself, you can read the OIDC specification.

Some IDPs, such as Okta, have their own dedicated connection templates in ACP, which you’re strongly recommended to use whenever possible. Use the generic OIDC connector only to bind OIDC-compliant IDPs which do not have a dedicated connection template in ACP.


  • Your IDP must implement the OIDC specification.

  • You must have an OAuth application registered with your IDP.

    1. Create an OAuth application with your IDP. Follow the IDP documentation for help.

      Redirect URL for your application

      When prompted for the redirect URL, use the Redirect URL from ACP as explained in step 2 under Connect IDP. Use this Redirect URL in your application configuration.

    2. Configure your application to

      • Use the authorization code grant flow
      • Request the following scopes: openid, email, and profile.

Connect IDP

  1. In your workspace, go to Identities -> Create Identity.


    A list of identity provider templates is displayed.

  2. Select the OpenID Connect template and click Next.


    The Register OpenID Connect form opens. You can now use the redirect URL to complet registering an OAuth application with your IDP.

  3. In the Register OpenID Connect form, enter the Issuer URL, Client ID, and Client Secret.

    Parameter Description
    Issuer URL URL where ACP can find the OpenID configuration of the IDP. Use the bare URL of the issuer, for example Do not append /.well-known/openid-configuration.
    Client ID Client ID of the OAuth application registered with your IDP
    Client secret Secret of OAuth application registered with your IDP
  4. Optionally, enable Authentication context caching.


    You can enable the authentication context caching if you wish to store the user’s authentication context locally. If you do, specify the cache Time To Live as well. Learn more by reading Stateful authorization with ACP.

  5. Select Save.


    Your new IDP connection is created. Users can now authenticate via the OIDC-compliant IDP.

Configure advanced settings

To configure your new IDP advanced settings

  1. From the Identities -> YOUR_IDENTITY -> Configuration page, select Advanced settings at the bottom.

  2. In the Scopes field, add scopes to be returned in the IDP response after user authentication.


    Since multiple clients can use the same IDP for user authentication, you may need to further restrict specific client’s ability to request a given scope. For more information, read about Configuring applications in ACP.

  3. In the Authentication Method Reference you can select an authentication method to be written into the amr object returned by the IDP. The amr object is written if it doesn’t exist. If it exists, its values are replaced with the selected item.

  4. Optionally, enable the Get user info option.


    If you enable the Get user info option, the connector calls the OIDC userinfo endpoint to retrieve additional user attributes.

  5. Select Save.

Add custom IDP attributes

If your IDP returns custom claims outside of the standard OIDC/SAML scope, make sure to add them to the IDP connector so that they can be recognized and mapped to the authentication context.

  1. Go to Identities and select an IDP from the list.

  2. Open the Attributes page. A standard list of attributes returned by this IDP appears. In most cases, these attributes conform either to the OIDC or SAML specification.

  3. Select Add attribute.

  4. In Source, select the data source for the custom attribute

    Source Description
    Access token Get data from the access token received from the IDP
    ID token Get data from the ID token received from the IDP
    User info Get data data returned by the OIDC user info endpoint (note that this must be explicitly enabled on the IDP connector)
  5. Fill in the rest of the form.

    Option Description
    Claim name Name of your custom attribute
    Display name User-friendly name for the custom attribute
    Data type Data type matching that of the incoming IDP claim
  6. Save your changes and proceed to mapping the attributes to the authentication context.

Map IDP attributes to authentication context

If you’ve added custom attributes for an IDP, you need to make sure they are mapped to the authentication context. You can do it either from the IDP configuration page (as explained here) or use Data Lineage instead.

Default OIDC/SAML attributes are mapped out of the box.

  1. Go to Identities and select an IDP from the list.

  2. Open the Mappings page. A standard attribute mapping for this IDP appears.

  3. Select Add mapping and map any custom IDP attributes to an existing authentication context attribute.


    If you need to create new authentication context attributes, read Setting up authentication context.

  4. Optionally, assign a post-authentication extension to modify your authentication context before issuing the token to the client.

  5. Save your changes. Your mapped custom attributes should now be shared in the ID token issued to your client application, given that the target application requests them (you can check this in Data Lineage).

Test your IDP


Your provider is configured as a user-authentication method by your administrator. Demo workspace is available.


  1. Open the user portal.

  2. Select LOGIN TO DEMO APP.

  3. Select your configured IDP and, next, authenticate in IDP.


ACP displays the consent page that lists data scopes to be shared with the application. When you proceed to the application (ALLOW ACCESS), the PII data coming from IDP is delivered through the access token and the ID token generated by ACP.

Read more

For information on granting and managing ACP consents, see ACP OAuth consents.