You can integrate Identity Providers with Identity as a Service to allow authentication with either IDaaS or the Identity Provider. When integrated, IDaaS acts as an SAML or OIDC client to connect to the Identity Provider. For example, you configure Application XYZ as the Identity Provider and integrate it with IDaaS. When you log in to IDaaS you have the option to log in using IDaaS authentication or log in to Application XYZ using your Application XYZ credentials.
Before you begin, you need to obtain the following from your OIDC Identity Provider:
● Client ID
● Client Secret
● Issuer URL
Additionally, you need the following values. You may be able to fetch these values from the Identity Provider once you have entered the Issuer URL:
● Authorization Endpoint
● Token Endpoint
● User Info Endpoint
● Revocation Endpoint
● JWKS URI
Before you begin, you need to obtain the following from your SAML Identity Provider:
● SP Entity ID
● SSO endpoint
● Identity Provider verification certificate (one or two)
● Optional values:
– Issuer, for example the Entity ID of the Identity Provider.
– Assertion Consumer Service URL if you are using a proxy server.
Note: To integrate a generic SAML or OIDC Identity Provider, see Manage Identity Providers.
Topics in this section:
● Integrate Microsoft Azure AD
● Integrate Nets E-Ident IDP Broker
● Integrate Identity Verification as a Service