Redirect URIs are a required part of any OAuth 2.0 or OpenID Connect integration. After a user completes the authorization flow, ID.me redirects them back to your application using the specified redirect_uri. This URI may include sensitive information, so it’s critical that redirection only occurs to trusted, pre-configured locations.
redirect_uri must be configured and included in the authorization request to begin the OAuth or OIDC flow*) and URI fragments (#) are not supportedProperly managing your redirect URIs helps secure your integration and ensures reliable user redirection back to your application
To help keep your application secure, configure your redirect URIs as static callback URLs. These should only allow the following parameters:
Authorization code flow
codestateid_token (if applicable)You can update and manage your redirect URIs directly from the developer dashboard by following these steps:
To configure a localhost or ngrok URI for development, please contact your ID.me solution consultant or email partnersupport@id.me