Migrating to OIDC

📘

Important Note Regarding OIDC

Before proceeding, please ensure you are familiar with the /userinfo endpoint and how to obtain an id_token. You will also need to have OIDC scopes applied to your application. If you are unsure if your application is configured for OIDC, please reach out to Clever Support.

Migrating to OIDC from OAuth 2.0

There are two ways you can update your SSO integration to use OIDC instead of the default OAuth 2.0 flow:

• Use the access_token received from a successful POST to /oauth/tokens to make a GET call to https://api.clever.com/userinfo
• Decode the id_token received from a successful POST to /oauth/tokens to obtain user data (requires OIDC scopes for your Clever SSO app)

Migrating to OIDC from SAML

Clever SSO applications cannot support a SAML integration and an OIDC integration for the same application. To begin using OIDC in your SSO integration, you will first need to have a new app created. Please reach out to Clever Support to request a new application with OIDC scopes.

Once you've obtained an OIDC-enabled application, you can begin development on your new OIDC integration. We recommend reviewing these pages for more information on OIDC integrations:

• OAuth and OIDC Overview
• OIDC Implementation