ID.me
ID.me provides consumer identity proofing and federated SSO. Developers can integrate via OIDC/OAuth 2.0 (with ID and access tokens) or configure ID.me as a SAML 2.0 IdP with attribute bundles. ID.me advertises issuance of IAL2/AAL2-compliant credentials and multiple verification pathways (online, video chat “trusted referee,” and in-person).
Key Capabilities
-
Standards-based SSO: Works as an OIDC provider and SAML 2.0 IdP; docs cover flows, tokens, and SAML configuration for common stacks.
-
NIST-aligned verification: ID.me states support for NIST 800-63-3 IAL2/AAL2 identity proofing and authentication.
-
Multiple proofing options: Automated online verification, virtual in-person (video call with a Trusted Referee), and in-person sites to handle edge cases.
-
MFA & passkeys: MFA choices include WebAuthn passkeys plus traditional factors; guidance is provided in developer docs.
Limitations
-
Policy & public-sector sensitivities: ID.me’s use of face recognition in some verification flows has drawn scrutiny; agencies have adjusted policies over time
-
Provisioning scope: Documentation centers on SSO and verification; there is not enough public information to confirm a customer-facing SCIM 2.0 provisioning API.
-
Token/profile breadth: Attribute release is controlled via policy-defined “bundles” and scopes; apps needing rich profiles should confirm available claims/attributes per integration.
-
Short-lived API tokens: OIDC access_token lifetimes are intentionally brief (e.g., 5 minutes).