Skip to content

Manage Providers

This page covers the day-to-day management of sign-in providers in the Providers tab: testing, editing, enabling, disabling, and deleting them. You can search providers by name and sort them by name or created date.

Permissions

Only users with the Admin role can manage sign-in providers. See the Permissions page for details.

Test a Provider

The Test button at the bottom of the provider form runs connection diagnostics for OIDC and SAML providers, against the values currently in the form (or the saved configuration when nothing was changed).

test-provider-results

The results list each check with a Passed, Failed, Warning, or Skipped badge; expand a check to read the details. The checks cover, depending on the provider type: the discovery document or metadata fetch, the authorization, token, UserInfo, and SSO endpoints, the signing keys and certificate validity, the client credentials, the scopes, the redirect URI, the attribute or claim mapping, the groups claim, the generated service provider metadata, and the sign-in flow initiation.

Tip

Test a provider before enabling it, and again after any change to its endpoints or certificates. Diagnostics do not apply to the Email & Password provider, which has no external connection to test.

Edit a Provider

Step 1: Click the vertical ellipsis next to the provider you want to edit.

step-1-click-ellipsis

Step 2: A menu appears with the available actions. Click Edit .

step-2-click-edit

Step 3: Update the fields as needed. Secrets (client secret, certificate) are never displayed; enter a new value only to replace the stored one.

step-3-edit-modal

Step 4: Click the Save button.

step-4-click-save

Step 5: A success message appears.

step-5-success

Some changes sign users out

Saving a security-sensitive change (credentials, certificates, or a more restrictive domain or group policy) ends every active session issued by the provider, including your own if you signed in with it. The form warns you first, lists the changes that caused it, and asks you to confirm with Save and Sign Everyone Out.

Editing the provider you signed in with

When you edit the provider your own session signed in with, any change that affects sign-in is saved only after the connection diagnostics pass. That covers the endpoints and metadata, certificates and client credentials, scopes, the claim or attribute mapping, and the groups claim. If a check fails, the form names the failing checks so you can correct the values and try again.

Enable or Disable a Provider

Each provider row has an Enabled / Disabled control:

  • Enable makes the provider available on the sign-in page (once your deployment uses the new authentication mode).
  • Disable immediately ends every active session issued by the provider, including your own if you signed in with it.

Step 1: Click Enabled on the provider's row.

enable-provider

Step 2: A success message appears.

enable-success

Step 1: Click Disabled on the provider's row.

disable-provider

Step 2: A confirmation dialog explains that every active session issued by the provider ends. Click Disable and Sign Everyone Out to proceed.

disable-confirmation

Step 3: A success message appears.

disable-success

Note

Once your deployment signs in through these providers, the last enabled provider cannot be disabled, and you cannot disable the provider your current session signed in with. This keeps you from locking everyone (or yourself) out.

Delete a Provider

Step 1: Click the vertical ellipsis next to the provider you want to delete.

step-1-delete-ellipsis

Step 2: A menu appears with the available actions. Click Delete .

step-2-click-delete

Step 3: A confirmation modal appears showing the provider's name and type. Deleting a provider removes all of its configuration and cannot be undone.

step-3-delete-modal

Step 4: Click the Delete button to confirm. A success message appears and the provider leaves the list.

step-4-delete-success

Note

A provider with users still associated to it cannot be deleted; disable it instead. Deletion is permanent, so prefer disabling when you may need the configuration again.