Choosing an identity provider
You usually don’t choose the identity provider; your organisation already has one. What you choose is how rConfig connects to it. Several providers can connect two ways, and the choice decides whether the identity provider can manage rConfig roles.
The connections
| Connection | Protocol | Approval and roles | Set up in |
|---|---|---|---|
| Microsoft (Entra ID) | OAuth | Manual, in Users | .env. Commercial, GCC High, DoD and China clouds |
| Okta | OpenID Connect | Manual, in Users | .env |
| Google Workspace | OAuth 2.0 | Manual, in Users | .env |
| Shibboleth | SAML 2.0 | Manual, or auto-approve and role mapping (V8.3.3 and later) | Shibboleth configuration and the SAML2 / SSO page |
| Generic SAML 2.0 | SAML 2.0 | Manual, or auto-approve and role mapping (V8.3.3 and later) | IdP metadata and the SAML2 / SSO page |
Other providers from the Socialite Providers library can be added on request through rConfig support.
SAML or OAuth?
Entra ID and Okta can both act as SAML 2.0 identity providers as well as OAuth ones, so rConfig can reach them either way:
- Use the provider’s own OAuth connection when approving users and assigning roles by hand in rConfig is fine. It’s the quicker set-up.
- Use generic SAML 2.0 when you want the identity provider’s groups to decide rConfig access and roles. Only the SAML connections support auto-approve and role mapping.
By provider
- Microsoft Entra ID. OAuth for a quick start. SAML through the generic connection for role mapping from Entra groups, which can send group names or object IDs. See the worked Entra examples in SAML role mapping.
- Okta. OpenID Connect for a quick start, or an Okta SAML app through the generic connection for role mapping.
- Google Workspace. OAuth. Approval and roles stay manual.
- Shibboleth. For universities and research networks that federate through Shibboleth. SAML, so role mapping is available.
- ADFS and other SAML 2.0 providers. The generic SAML connection. ADFS usually sends groups as distinguished names, which the Group DN match mode reads directly.
SSO, LDAP or RADIUS?
SSO isn’t the only way to use central accounts. LDAP authenticates against your directory directly and has its own group to role mapping; RADIUS uses the server your network team may already run. The trade-offs between all three, including what happens when the external service is down, are compared in the Security guides.
Choose SSO when you want the identity provider’s MFA and conditional access in front of rConfig. Whatever you choose, keep a local administrator account for when it’s unavailable.