Migrating to OIDC

Use this page to migrate an existing Clever SSO integration from OAuth 2.0 or SAML to OIDC.

❗️

Before you start

Make sure you understand how to use the /userinfo endpoint and how to obtain an id_token.

Your application must also have OIDC scopes enabled. If you are not sure whether your app is configured for OIDC, contact Clever Support.

Migrate from OAuth 2.0 to OIDC

If your app already uses the standard Clever OAuth flow, you can move to OIDC in two ways:

• Use the access_token returned from POST /oauth/tokens to call https://api.clever.com/userinfo
• Decode the id_token returned from POST /oauth/tokens to obtain user identity data
  • this requires OIDC scopes on your Clever SSO application

For implementation details, review:

• OAuth Implementation
• OIDC Implementation
• The /userinfo Endpoint

Migrate from SAML to OIDC

A Clever SSO application cannot support both SAML and OIDC on the same application.

If you want to move from SAML to OIDC, request a new OIDC-enabled application from Clever Support.

After you receive the new application, build and test your OIDC integration using the OIDC-specific documentation:

• OIDC Implementation
• The /userinfo Endpoint