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 OIDC issuer for v2 is https://connect.hopae.com for every app. If your sandbox integration validated https://sandbox.connect.hopae.com, update it when you move to /v2/auth. 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.
  • Errors use one envelope: { "error": { "code", "message" }, "request_id" }.
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

Move the claims you sent in requestedClaims to the workflow’s Claims tab. 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 does not map 1:1 to a v2 connectionId. A v1 provider corresponds to a v2 provider, and a provider offers one connection per credential it can present. Some v1 providers covered several credentials at once (for example us-id-pass covered Google Wallet passports from several countries and Aadhaar), so they become several connections in v2. To find yours:
  1. Open Configuration → Connections in the Console and filter by provider or country.
  2. Pick the row whose credential matches what your v1 integration verified. Its Connection ID is the value you use.
  3. Activate it, and repeat for every credential you need.
The same information is available from Get Connections: each item carries provider.id, credential.id, and connectionId. If you are unsure which connection replaces a v1 provider, ask support@hopae.com with the v1 providerId and we will map it for you.