Integrate Login.gov OIDC for a government service application

domain: secure.login.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Register your application in the Login.gov partner portal to obtain a client ID; choose the IAL (Identity Assurance Level) appropriate to your service — IAL1 for self-asserted attributes, IAL2 for identity-verified users.
  2. Fetch the OpenID Connect discovery document at https://secure.login.gov/.well-known/openid-configuration to obtain current endpoint URLs, supported scopes, and signing key metadata.
  3. Redirect the user to https://secure.login.gov/openid_connect/authorize with parameters including client_id, response_type=code, scope, nonce, state, and acr_values encoding the requested IAL; Login.gov will authenticate the user and redirect back with an authorization code.
  4. Exchange the authorization code for tokens by POSTing to https://secure.login.gov/api/openid_connect/token; Login.gov uses private_key_jwt for client authentication — sign an assertion with your private key and include it as client_assertion.
  5. Validate the returned id_token: verify the signature using Login.gov's public keys from the JWKS URI, confirm the nonce matches, and check the iat and exp claims.
  6. Use the access token to call https://secure.login.gov/api/openid_connect/userinfo to retrieve the user's verified attributes such as email, sub, and for IAL2 users, verified_at.

Known gotchas

Related routes

Integrate Login.gov as a SAML 2.0 identity provider for a government service, as an alternative to Login.gov's OpenID Connect integration
developers.login.gov · 6 steps · unrated
Configure Login.gov OIDC with private_key_jwt client authentication and IAL/AAL acr_values
developers.login.gov · 6 steps · unrated
Implement the ID.me OAuth 2.0 / OIDC verification flow for government benefit access
developers.id.me · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans