» OIDC Provider Configuration

This page collects high-level setup steps on how to configure an OIDC application for various providers. For more general usage and operation information, see the Vault JWT/OIDC method documentation.

OIDC providers are often highly configurable and you should become familiar with their recommended settings and best practices. The instructions below are largely community-driven and intended to help you get started. Corrections and additions may be submitted via the Vault Github repository.

» Azure Active Directory (AAD)

Reference: Azure Active Directory v2.0 and the OpenID Connect protocol

  1. Register or select an AAD application. Visit Overview page.
  2. Configure Redirect URIs ("Web" type).
  3. Record "Application (client) ID" as you will need it as the oidc_client_id
  4. Under API Permissions grant the following permission:
  5. Under "Endpoints", copy the OpenID Connect metadata document URL, omitting the /well-known... portion.
  6. Switch to Certificates & Secrets. Create a new client secret and record the generated value as it will not be accessible after you leave the page.

Please note Azure AD v2.0 endpoints are required for external groups to work.

  • groupMembershipClaims should be changed from none in the App registration manifest. Options are "All" or "Security"

  • In the OIDC Role config the scope "https://graph.microsoft.com/.default" should be added to add groups to the jwt token and groups_claim should be set to groups.

  • Finally Azure AD group can be referenced by using the groups objectId as the group alias name for the external group.

» CLI setup instructions:

You have to fill in the following values make sure to use the correct vault secret path that matches the name of the authentication method such as /oidc/ * oidc_client_id = Application Client ID * oidc_client_secret = Secret obtained from the Certificates & Secrets Section * default_role = default role the user will be using when connecting. (see the second command) * oidc_discovery_url = Open ID endpoint retrieved from the App Registration wections. vault write auth/oidc/config \ oidc_client_id="your_client_id" \ oidc_client_secret="your_client_secret" \ default_role=“your_default_role” \ oidc_discovery_url="https://login.microsoftonline.com/tenant_id/v2.0”

vault write auth/oidc/role/demo user_claim="email" \
    allowed_redirect_uris="http://localhost:8250/oidc/callback,https://online_version_hostname:port_number/ui/vault/auth/oidc/oidc/callback"  \
    groups_claim="groups" \
    policies=default

» Auth0

  1. Select Create Application (Regular Web App).
  2. Configure Allowed Callback URLs.
  3. Copy client ID and secret.
  4. If you see Vault errors involving signature, check the application's Advanced > OAuth settings and verify that signing algorithm is "RS256".

» Gitlab

  1. Visit Settings > Applications.
  2. Fill out Name and Redirect URIs.
  3. Making sure to select the "openid" scope.
  4. Copy client ID and secret.

» Google

Main reference: Using OAuth 2.0 to Access Google APIs

  1. Visit the Google API Console.
  2. Create or a select a project.
  3. Create a new credential via Credentials > Create Credentials > OAuth Client ID.
  4. Configure the OAuth Consent Screen. Application Name is required. Save.
  5. Select application type: "Web Application".
  6. Configure Authorized Redirect URIs.
  7. Save client ID and secret.

» Keycloak

  1. Select/create a Realm and Client. Select a Client and visit Settings.
  2. Client Protocol: openid-connect
  3. Access Type: confidential
  4. Standard Flow Enabled: On
  5. Configure Valid Redirect URIs.
  6. Save.
  7. Visit Credentials. Select Client ID and Secret and note the generated secret.

» Okta

  1. Make sure an Authorization Server has been created.
  2. Visit Applications > Add Application (Web).
  3. Configure Login redirect URIs. Save.
  4. Save client ID and secret.

Note your policy will need oidc_scopes to include profile to get a full profile ("Fat Token"). You will also need to configure bound audience along the lines of "bound_audiences": ["api://default", "0a4........."] if you are using the default authorization server.