--- title: "How to Manage Identity Providers" slug: "how-to-manage-identity-providers" updated: 2026-11-05T17:05:18Z published: 2026-11-05T17:05:18Z canonical: "docs.discngine.com/how-to-manage-identity-providers" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.discngine.com/llms.txt > Use this file to discover all available pages before exploring further. # How to Manage Identity Providers > ⚠️ **Role required:** The features described in this guide require the **Organisation Administrator** role. If you do not have this role, contact your organisation's administrator. Identity Providers (IdPs) manage user authentication for your organisation. They allow users to log in using their corporate credentials via OpenID Connect (OIDC) or SAML protocols, enabling single sign-on (SSO) across all Discngine applications. ## Navigation Click on **Identity Providers** in the left sidebar or on the **Identity Providers** card on the home page. ![IdP Navigation](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Setting/IdP_navigation.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A35%3A22Z&se=2026-11-16T06%3A35%3A22Z&sr=b&sp=r&sig=hvviOFdcDNLEpTJHeuajzQ%2BicAB3gzWZrqsLnhGKr1c%3D) The Identity Providers page shows: | Column | Description | | --- | --- | | **Provider Name** | The name of the identity provider | | **Provider Type** | The protocol type (e.g., "OpenID Connect with Issuer URL", "Security Assertion Markup Language (SAML)") | | **Status** | Whether the provider is currently enabled or disabled | | **Secret / certificate expiry** | The expiry date recorded for the provider's client secret or signing certificate, used for renewal reminders. **No expiry set** means no reminder will be sent; an expired date shows in red | At the top of the page: - **OIDC metadata**: View the OIDC metadata for your organisation (useful for configuring relying parties) - **New Provider**: Add a new identity provider ## How to Add an Identity Provider 1. Click **New Provider**. The panel opens with **Provider Type** set to *OpenID Connect*. 2. Choose the **Provider Type**: - **OpenID Connect** — enter the provider's explicit endpoints (Authorization URL, Token URL, User Info URL). - **OpenID Connect with Issuer URL** — the simplest option: enter only the **Issuer URL** and the endpoints are discovered automatically. Recommended when your provider supports OIDC discovery (Azure AD, Okta, Cognito…). - **Security Assertion Markup Language (SAML)** — for providers that use SAML 2.0. 3. Fill in the fields for the chosen type. **For OpenID Connect with Issuer URL** (recommended): ![New Provider dialog configured for OpenID Connect with Issuer URL.](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Setting/new_idp_oidc_issuer.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A35%3A22Z&se=2026-11-16T06%3A35%3A22Z&sr=b&sp=r&sig=6YculBp02acm6xkev1CDsnPvGMomr%2BftEuvaGpqG%2BGk%3D) | Field | Description | Required | | --- | --- | --- | | **Provider Name** | A descriptive name (e.g., "Corporate Azure AD") | Yes | | **Issuer URL** | The OIDC issuer URL from your provider (e.g., `https://login.microsoftonline.com/{tenant}/v2.0`) | Yes | | **Client ID** | The application / client ID from your provider | Yes | | **Client Secret** | The client secret from your provider | Yes | (Plain **OpenID Connect** asks instead for the explicit **Authorization URL**, **Token URL** and **User Info URL**.) For OpenID Connect, copy the **Web Redirect URI** shown in the panel and add it as an allowed redirect / callback URI in your identity provider. **For SAML** — setup is a **two-step** process: ![New Provider dialog configured for SAML.](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Setting/new_idp_saml.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A35%3A22Z&se=2026-11-16T06%3A35%3A22Z&sr=b&sp=r&sig=8JohV8bMc2fyCseVrhVwhqne6zy%2BwO37v3KGcW5EtmQ%3D) | Field | Description | Required | | --- | --- | --- | | **Provider Name** | A descriptive name (e.g., "Corporate SAML") | Yes | | **IdP Endpoint** | Your provider's SAML SSO (login) URL | Yes | | **Email Claim** | The SAML attribute that carries the user's email (a sensible default is pre-filled) | Yes | | **Certificate** | Your provider's X.509 signing certificate (can be added now or later) | Yes | 1. Create the provider with at least the **IdP Endpoint** and click **Save**. 2. Copy the generated **Identifier (Entity ID)** and **Reply URL** from the panel into your identity provider (Azure AD, Okta, …). 3. Download the signing certificate from your provider and upload it in the **Certificate** field. 4. For an OpenID Connect provider, set the **Secret / certificate expiry** date of the client secret: it is required as soon as a secret is entered, and the Admin Center reminds the provider's managers before it expires. For SAML, the date is read from the uploaded certificate. 5. Click **Test** to validate the configuration, then **Save**. > For provider-specific configuration instructions with screenshots, see the provider setup guides below. The generic **OpenID Connect with Issuer URL** steps above work for any OIDC-compliant provider that is not listed. > > > - [Azure AD / Microsoft Entra ID](/public/docs/azure-ad-microsoft-entra) > - [Okta](/public/docs/okta) > - [Amazon Cognito](/public/docs/amazon-cognito) > - [GitHub](/public/docs/github) > - [SAML 2.0](/public/docs/configure-saml-security-assertion-markup-language) ## How to Modify an Identity Provider 1. Click **Edit** next to the desired Identity Provider. 2. Update the necessary fields (e.g., rotate a client secret, update the issuer URL). 3. Click **Save**. When you enter a new OpenID Connect client secret, also enter the expiry date of that new secret: the save is refused if the date is empty, in the past or unchanged. A recorded date can be corrected but not cleared. > **Tip**: When rotating a client secret, update the secret in your IdP provider first, then update it in the Admin Center immediately after to avoid login disruption. ## How to Rotate an Expiring Client Secret The Admin Center emails your organisation's administrators 30 days and 7 days before a provider's client secret or signing certificate expires. Rotate it before that date: after it, users of the applications that sign in through the provider can no longer log in. 1. Ask the team that manages your identity provider (Microsoft Entra ID, Okta…) for a new client secret and its expiry date, quoting the provider's **Client ID** so they renew the right app registration. For SAML, ask for the new signing certificate of the provider's **Identifier (Entity ID)**. 2. On the Identity Providers page, click **Edit** next to the provider. 3. Enter the new credential: - **OpenID Connect**: paste the new **Client Secret** and set the new **Secret / certificate expiry** date. - **SAML**: upload the new certificate in the **Certificate** field. Its expiry date is read from it. 4. Click **Test**, then **Save**. ## How to Delete an Identity Provider 1. Click **Edit** next to the desired Identity Provider. 2. Click **Delete**. 3. Confirm the deletion. > **Warning**: Deleting an IdP means users who rely on it for SSO will no longer be able to log in via that provider. Ensure affected users have local login enabled before deleting. ## Enabling a provider for specific applications A provider can be enabled per application, so that only the applications you choose offer sign-in through it. ![The Application Registration tab lists your applications grouped by environment, each with an Enabled toggle.](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Setting/idp_application_registration.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A35%3A22Z&se=2026-11-16T06%3A35%3A22Z&sr=b&sp=r&sig=DgpsgAcgbeBehZ3uusPgS5K6cqdmWgLbDDfn5CutAg0%3D) 1. Open the provider by clicking its name (or **Edit**) on the Identity Providers page. 2. Switch to the **Application Registration** tab. 3. Your applications are listed grouped by environment. Turn the **Enabled** toggle on for each application that should use this provider for sign-in (and off for those that should not). 4. Click **Save**. ## Related - [Organisation Administrator Guide](/public/docs/organisation-administrator)