Identity providers
Use existing enterprise or consumer identities to authenticate users in SecureAuth. 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.
In this sectionβ
ποΈ Auth0
Users in your Auth0 tenant can access applications registered in SecureAuth.
ποΈ AWS Cognito
Users in your AWS Cognito tenant can access applications registered in SecureAuth.
ποΈ Azure AD - OIDC
Users in your Azure Active Directory (AD) tenant can access applications registered in SecureAuth.
ποΈ Azure AD - SAML
Users in your Azure Active Directory (AD) tenant can access applications registered in SecureAuth.
ποΈ Azure B2C
Instructions on how to configure an Azure B2C as an IdP.
ποΈ Custom
Instructions on how to connect your authentication providers that are neither SAML/OIDC compliant to SecureAuth.
ποΈ Entrust
Instructions on how to connect the Entrust IDP to SecureAuth.
ποΈ External
Learn how to integrate SecureAuth with an external datastore IDP.
ποΈ GitHub
Users in your GitHub tenant can access applications registered in SecureAuth.
ποΈ Keycloak
Users in your Keycloak tenant can access applications registered in SecureAuth.
ποΈ Okta - OIDC
Learn how to configure Okta and SecureAuth to enable your users to sign in using Okta IDP.
ποΈ Okta - SAML
Learn how to configure Okta and SecureAuth to enable your users to sign in using Okta IDP and SAML
ποΈ OpenID
Instructions on how to connect an OIDC-compliant Identity Provider to Authorization Control Plane.
ποΈ Salesforce
Users in your Salesforce tenant can access applications registered in SecureAuth.
ποΈ SAML IdP
Instructions on how to connect a SAML-compliant IDP to SecureAuth.