Identity providers
Use existing enterprise or consumer identities to authenticate users in SecureAuth Connect. You can connect OIDC or SAML providers, use SecureAuth Identity Pools, or add a custom identity source when you have legacy or non-standard systems.
💡 Why this matters
You reduce sign-in friction and centralize policies while supporting partners and customers who bring their own IdP.
Configuration topics​
These topics apply across providers.
- IdP routing – narrow which identity sources appear in the login flow.
- SAML IdP assertion attributes – map SAML attributes to your authentication context.
Vendor-specific guides​
Set up an integration with a specific identity provider.
- Active Directory
- Auth0
- AWS Cognito
- Azure AD (OIDC)
- Azure AD (SAML)
- Azure B2C
- Entrust
- GitHub
- Keycloak
- Okta (OIDC)
- Okta (SAML)
- OneLogin
- Salesforce
Generic providers​
Use these when your vendor isn't listed above.
- OpenID generic – any OIDC-compliant identity provider.
- SAML IdP (generic) – any SAML-compliant identity provider.
Custom integrations​
For non-standard or legacy systems that don't fit OIDC or SAML patterns.
- Custom identity source – non-OIDC/SAML authentication providers.
- External datastore – external identity datastores.