Skip to main content
Your v1 integration keeps working while you move. Use your app’s App ID and App Secret from Developers → API Settings.

What changes in your code

Sandbox and production apps use the same v2 URLs. The credentials select the app. See Apps & Environments.
The v2 OIDC issuer is https://connect.hopae.com when you call connect.hopae.com. If you keep calling sandbox.connect.hopae.com, the issuer is https://sandbox.connect.hopae.com. See OIDC Integration.
v1 request
v2 request

What changes in the result

user and match are unchanged. Check these details:
  • provenance and missing_claims are opt-in: add provenance=true and missing_claims=true to the userinfo request.
  • Provider ids are catalog ids (smart-id, not smartid), and there is no amr. The connection that ran is in provenance._metadata.
  • provenance.presentation.credentials[] holds only the source’s claims and evidence.
  • source_id is returned only when Source ID is ticked on the workflow’s Claims tab, or when requestedClaims lists it.
  • Errors use one envelope: { "error": { "code", "message" }, "request_id" }.
  • A finished verification is completed or failed, and result.code says how it ended. Read userinfo only when it is RECEIVED. See Result Codes.
See Return Data.

Webhooks

Turn on the Webhook v2 endpoint under Developers → Webhooks when your receiver handles the v2 format, then turn Webhook v1 off. You can run both while you switch. See Webhooks.

Step by step

1

Find your connections

Look up the connection ID for each v1 provider you use (below), and check that it is activated and enabled in the workflow.
2

Set the claims

Set the claims you sent in requestedClaims on the workflow’s Claims tab, or keep sending requestedClaims. A non-empty list replaces the workflow’s claims. See Workflows.
3

Update your code and test with a sandbox app

Apply the changes above and run the flow with test credentials. See Sandbox Testing.
4

Switch production

Deploy the same changes with your production app’s credentials.

Finding your connections

A v1 providerId corresponds to a v2 provider, and a provider offers one connection per credential it can present. Most v1 providers become one connection. us-id-pass covered Google Wallet passports from several countries, so it becomes one connection per country. For each v1 provider you use, find its connections in the table below. Then activate them under Configuration → Connections in the Console and enable them in your workflow. Get Connections returns connectionId, provider.id, and credential.id for each.
Instead of connectionId, a v2 request can name providerId (with an optional credentialId). That is the v2 provider.id from Get Connections, which can differ from the v1 providerId. See Create Verification.
If a v1 provider you use is not listed, ask support@hopae.com with its providerId.