Configuration from the IdP's perspective

About 1 min

Configure an IdP

The Datawiza Access Proxy (DAP) integrates with external Identity Provider (IdP) like Microsoft Entra ID (Azure Active Directory) and Okta to enable single sign-on (SSO) authentication so that application developers don't have to write the integration code.
Also DAP obtains the user info from IdP and enforces the access policies based on user attributes.

Currently, we support Auth0, Cognito, Github, Google social account, Google Workspace (G Suite), Keycloak, Microsoft Entra ID (Azure Active Directory (AD)), Microsoft Azure Active Directory (AD) B2C, Microsoft Entra ID (Azure Active Directory (AD)) SAML, Okta, PingOne, and Twitter. Supporting more IdPs (including PingIdentity, OneLogin, etc.) is on our roadmap and will be available soon.

For each DAP deployment, you need to configure a SSO application with LDAP, OAuth, OpenID Connect (OIDC) or Security Assertion Markup Language (SAML) on your IdP platform.
Each DAP deployment is associated with one SSO application on IdP.

The following configuration guides provide instructions on how to configure a specific SSO application for a DAP deployment, but DAP can support any IdP.
If you don't see your IdP listed below, refer to these guides as examples or contact us via info@datawiza.com: