Create an OpenID Connect app in Login.gov, add the redirect URI from this setup, assign your users and enter the app’s issuer and credentials here.
The values in braces, such as {redirect_uri}, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.
-
Create an OIDC app
Section titled “Create an OIDC app”In the Login.gov Partner Portal, create an app for this integration in the sandbox first, and choose OpenID Connect with private_key_jwt as the authentication method.
-
Add the redirect URI
Section titled “Add the redirect URI”Add
{redirect_uri}to the app’s sign-in redirect URIs, exactly as shown. A redirect URI that differs by one character is refused.Paste into Login.gov:
- Redirect URI:
{redirect_uri}
Fixes:
oidc_token_exchange_failed - Redirect URI:
-
Upload the public certificate
Section titled “Upload the public certificate”Login.gov does not use client secrets. Upload the public certificate this setup gives you to the app in the Partner Portal. This app signs its token requests with the matching private key, which never leaves it.
Fixes:
oidc_token_exchange_failed -
Allow the sign-in scopes
Section titled “Allow the sign-in scopes”Allow the openid and email scopes. This setup asks for the authentication-only assurance level (urn:acr.login.gov:auth-only) on every sign-in, so you do not set acr_values yourself.
-
Enter the issuer and client ID
Section titled “Enter the issuer and client ID”Enter the app’s client ID (the issuer string you chose in the Partner Portal) in this setup. The provider’s issuer URL is “https://secure.login.gov/” in production; the sandbox uses its own address, listed in Login.gov’s developer documentation.
-
Test the connection
Section titled “Test the connection”Run a test sign-in in this setup, signing in as a user you assigned to the app.
-
Move to production
Section titled “Move to production”When test sign-ins work in the sandbox, request a production deployment of the app through the Partner Portal, then update the issuer URL and certificate in this setup if they changed.
Sources
Section titled “Sources”- OpenID Connect (Login.gov developer documentation), read on 2026-10-29
- OpenID Connect Core 1.0, read on 2026-10-29