Skip to main content
A connection is one way to verify an identity: a credential (what is proven, such as a US mobile driver’s license) presented through a provider (where it lives, such as Google Wallet). Each arrow above is one connection, for example google-wallet-us-mdl or smart-id. The same credential through three providers is three connections, because each provider has its own activation and availability.

​
Using a connection

  1. Activate it for your app. See Activate Connections.
  2. Enable it in a workflow. See Workflows.
  3. Verify with it over OIDC or REST.

​
Identifiers

A connection ID is readable but opaque. Do not parse it. Read provider.id and credential.id from Get Connections.

​
What a connection tells you

Get Connections and the connection’s detail sheet in the Console show:
  • Countries and the display name users see
  • Flow type: how the user completes it. See Verification Flow
  • Verification model: disclosure or match. See Verification Model
  • Level of assurance it can reach. See Assurance
  • Available claims, and the user input it needs. See User Input
The Console also shows whether a connection is available in Sandbox, Production, or both.
For how credentials and providers relate in depth, see Credentials & Providers.