Skip to content
Dashboard
Theme
Theme

Login.gov OIDC single sign-on

Set up OIDC single sign-on with Login.gov

View Markdown

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.

  1. 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.

  2. 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

  3. 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

  4. 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.

    Fixes: oidc_email_missing, oidc_email_not_verified

  5. 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.

    Fixes: oidc_discovery_unreachable, oidc_id_token_invalid

  6. Run a test sign-in in this setup, signing in as a user you assigned to the app.

  7. 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.