OAuth providers¶
Admin → Settings → OAuth Providers configures external identity providers — the other direction from OAuth clients: here Lurana BPM trusts a provider, instead of an application trusting Lurana BPM.
The list¶
The page supports filters: all, active, and disabled.
| Action | Effect |
|---|---|
| New provider | Creates a provider and reports Provider created |
| Disable | Moves it to Disabled and reports the change |
| Enable | Returns it to Active |
Some builds label the enable action Activate instead of Enable; the effect is the same, and the wording difference is worth reporting.
Modes¶
A provider runs in application mode (one client credential for the integration) or user delegation mode (the user authorises the provider). Choose the mode the integration expects. The form also configures the client ID, secret, redirect URI, scopes, and advanced endpoints.
Test and revoke¶
The provider detail can test the connection with a token and revoke the provider's access. Revoking stops new sign-ins through it; existing local accounts are not deleted.
The client secret¶
In the provider detail the Client secret is hidden by default, with Show secret and Copy next to it. It is never displayed in the list, only in the detail, and only on request.
Store the secret in your password manager: if it is lost, it has to be regenerated in the provider and pasted again.
Access control¶
Only administrators manage providers. A user without administrative permissions:
- does not see the menu entry;
- is refused if they open the address directly, even when they know it.
Test that with a real non-administrator account after configuring a provider — it is a two-minute check that catches a whole class of mistakes.
What a provider is used for¶
A configured provider lets users authenticate with the external identity service instead of a local password. The accounts still exist in the workspace, so disable the ones you do not want before enabling the provider for everyone.
Permissions¶
This page requires PM_SETUP. See
Permission reference.
Related¶
- OAuth clients — the opposite direction.
- Authentication sources — LDAP and Active Directory.
- Sign in — what the user sees.