1.5 KiB
1.5 KiB
layout | page_title | description |
---|---|---|
docs | OIDC Provider Setup - Auth Methods | OIDC provider configuration quick starts |
OIDC Provider Configuration
This page collects high-level setup steps on how to configure an OIDC application on various providers. Corrections and additions may be submitted via the Vault Github repository.
Auth0
- Select Create Application (Regular Web App).
- Configure Allowed Callback URLs.
- Copy client ID and secret.
- If you see Vault errors involving signature, check the application's Advanced > OAuth settings and verify that signing algorithm is "RS256".
Gitlab
- Visit Settings > Applications.
- Fill out Name and Redirect URIs.
- Making sure to select the "openid" scope.
- Copy client ID and secret.
Main reference: Using OAuth 2.0 to Access Google APIs
- Visit the Google API Console.
- Create or a select a project.
- Create a new credential via Credentials > Create Credentials > OAuth Client ID.
- Configure the OAuth Consent Screen. Application Name is required. Save.
- Select application type: "Web Application".
- Configured Authorized Redirect URIs.
- Save client ID and secret.
Okta
- Make sure an Authorization Server has been created.
- Visit Applications > Add Application (Web).
- Configure Login redirect URIs. Save.
- Save client ID and secret.