mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-10-08 08:27:53 +00:00
Merge branch 'feature/oidc' of https://github.com/Infisical/infisical into feature/oidc
This commit is contained in:
@@ -15,41 +15,41 @@ description: "Learn how to configure Auth0 OIDC for Infisical SSO."
|
|||||||
1.1. From the Application's Page, navigate to the settings tab of the Auth0 application you want to integrate with Infisical.
|
1.1. From the Application's Page, navigate to the settings tab of the Auth0 application you want to integrate with Infisical.
|
||||||

|

|
||||||
|
|
||||||
1.2. In the Application URIs section, set the appropriate values for the **Application Login URI**, **Allowed Callback URL**, and **Allowed Web Origins** fields.
|
1.2. In the Application URIs section, set the **Application Login URI** and **Allowed Web Origins** fields to `https://app.infisical.com` and the **Allowed Callback URL** field to `https://app.infisical.com/api/v1/sso/oidc/callback`.
|
||||||

|

|
||||||

|

|
||||||
<Info>
|
<Info>
|
||||||
If you’re self-hosting Infisical, then you will want to replace https://app.infisical.com with your own domain.
|
If you’re self-hosting Infisical, then you will want to replace https://app.infisical.com with your own domain.
|
||||||
</Info>
|
</Info>
|
||||||
|
|
||||||
Once done, click Save Changes.
|
Once done, click **Save Changes**.
|
||||||
|
|
||||||
1.3. Proceed to the Connections Tab and enable desired connections.
|
1.3. Proceed to the Connections Tab and enable desired connections.
|
||||||

|

|
||||||
|
|
||||||
</Step>
|
</Step>
|
||||||
<Step title="Retrieve Identity Provider (IdP) Information from Auth0">
|
<Step title="Retrieve Identity Provider (IdP) Information from Auth0">
|
||||||
2.1. From the application settings page, retrieve the values of **Client Id** and **Client Secret**
|
2.1. From the application settings page, retrieve the **Client ID** and **Client Secret**
|
||||||

|

|
||||||
|
|
||||||
2.2. In the advanced settings (bottom-most section), retrieve the OpenID Configuration URL from the Endpoints tab.
|
2.2. In the advanced settings (bottom-most section), retrieve the **OpenID Configuration URL** from the Endpoints tab.
|
||||||

|

|
||||||
|
|
||||||
We will need these values in the preceding steps.
|
Keep these values handy as we will need them in the next steps.
|
||||||
|
|
||||||
</Step>
|
</Step>
|
||||||
<Step title="Finish configuring OIDC in Infisical">
|
<Step title="Finish configuring OIDC in Infisical">
|
||||||
3.1. Back in Infisical, in the Organization settings > Security > OIDC, click Manage
|
3.1. Back in Infisical, in the Organization settings > Security > OIDC, click **Manage**.
|
||||||

|

|
||||||
|
|
||||||
3.2. For configuration type, select Discovery URL. Then, set the appropriate values for **Discovery Document URL**, **Client ID**, and **Client Secret**.
|
3.2. For configuration type, select **Discovery URL**. Then, set **Discovery Document URL**, **Client ID**, and **Client Secret** from step 2.1 and 2.2.
|
||||||

|

|
||||||
|
|
||||||
Once you've done that, press **Update** to complete the required configuration.
|
Once you've done that, press **Update** to complete the required configuration.
|
||||||
|
|
||||||
</Step>
|
</Step>
|
||||||
<Step title="Enable OIDC SSO in Infisical">
|
<Step title="Enable OIDC in Infisical">
|
||||||
Enabling OIDC SSO allows members in your organization to log into Infisical via Auth0.
|
Enabling OIDC allows members in your organization to log into Infisical via Auth0.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
|||||||
@@ -12,10 +12,10 @@ description: "Learn how to configure OIDC for Infisical SSO with any OIDC-compli
|
|||||||
|
|
||||||
You can configure your organization in Infisical to have members authenticate with the platform through identity providers via [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html).
|
You can configure your organization in Infisical to have members authenticate with the platform through identity providers via [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html).
|
||||||
|
|
||||||
**Prerequisites:**
|
Prerequisites:
|
||||||
|
|
||||||
- The identity provider (Okta, Google, Azure AD, etc.) should support OIDC.
|
- The identity provider (Okta, Google, Azure AD, etc.) should support OIDC.
|
||||||
- Users in the IdP should have a configured email and given_name.
|
- Users in the IdP should have a configured `email` and `given_name`.
|
||||||
|
|
||||||
<Steps>
|
<Steps>
|
||||||
<Step title="Setup Identity Provider">
|
<Step title="Setup Identity Provider">
|
||||||
@@ -32,15 +32,21 @@ You can configure your organization in Infisical to have members authenticate wi
|
|||||||

|

|
||||||
|
|
||||||
2.2. You can configure OIDC either through the Discovery URL (Recommended) or by inputting custom endpoints.
|
2.2. You can configure OIDC either through the Discovery URL (Recommended) or by inputting custom endpoints.
|
||||||
- If you want to configure via Discovery URL, you will have to use the URL with the following format: `https://<idp-domain>/.well-known/openid-configuration` as input for the **Discovery Document URL** field.
|
|
||||||
|
To configure OIDC via Discovery URL, set the **Configuration Type** field to **Discovery URL** and fill out the **Discovery Document URL** field.
|
||||||
|
|
||||||
|
<Note>
|
||||||
|
Note that the Discovery Document URL typically takes the form: `https://<idp-domain>/.well-known/openid-configuration`.
|
||||||
|
</Note>
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
- If you want to configure via the Custom option, you will have to define values for all the required endpoints.
|
To configure OIDC via the custom endpoints, set the **Configuration Type** field to **Custom** and input the required endpoint fields.
|
||||||

|

|
||||||
|
|
||||||
2.3. Optionally, you can define a whitelist of allowed email domains.
|
2.3. Optionally, you can define a whitelist of allowed email domains.
|
||||||
|
|
||||||
Fill up the **Client ID** and **Client Secret** fields and press **Update** to complete the required configuration.
|
Finally, fill out the **Client ID** and **Client Secret** fields and press **Update** to complete the required configuration.
|
||||||
|
|
||||||
</Step>
|
</Step>
|
||||||
|
|
||||||
|
|||||||
@@ -28,11 +28,11 @@ description: "Learn how to configure Keycloak OIDC for Infisical SSO."
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
1.4. In the Login Settings step, set the appropriate values for the following:
|
1.4. In the Login Settings step, set the following values:
|
||||||
- Root URL (base URL of Infisical)
|
- Root URL: `https://app.infisical.com`.
|
||||||
- Home URL (base URL of Infisical)
|
- Home URL: `https://app.infisical.com`.
|
||||||
- Valid Redirect URIs (`${INFISICAL_BASE_URL}/api/v1/sso/oidc/callback`)
|
- Valid Redirect URIs: `https://app.infisical.com/api/v1/sso/oidc/callback`.
|
||||||
- Web origins (base URL of Infisical)
|
- Web origins: `https://app.infisical.com`.
|
||||||
|
|
||||||

|

|
||||||
<Info>
|
<Info>
|
||||||
@@ -60,7 +60,7 @@ description: "Learn how to configure Keycloak OIDC for Infisical SSO."
|
|||||||
2.1. Back in Keycloak, navigate to Configure > Realm settings > General tab > Endpoints > OpenID Endpoint Configuration and copy the opened URL. This is what is to referred to as the Discovery Document URL and it takes the form: `https://keycloak-mysite.com/realms/myrealm/.well-known/openid-configuration`.
|
2.1. Back in Keycloak, navigate to Configure > Realm settings > General tab > Endpoints > OpenID Endpoint Configuration and copy the opened URL. This is what is to referred to as the Discovery Document URL and it takes the form: `https://keycloak-mysite.com/realms/myrealm/.well-known/openid-configuration`.
|
||||||

|

|
||||||
|
|
||||||
2.2. From the Clients page, navigate to the Credential tab and copy the value of Client secret for use in the preceding steps.
|
2.2. From the Clients page, navigate to the Credential tab and copy the **Client Secret** to be used in the next steps.
|
||||||

|

|
||||||
|
|
||||||
</Step>
|
</Step>
|
||||||
|
|||||||
Reference in New Issue
Block a user