OIDC
Start Authorization
Initiates the OIDC Authorization Code flow. Front‑channel redirect; no Authorization header.
GET
Initiate user authentication by redirecting the browser to Hopae Connect’s
/auth endpoint.
Query Parameters
Your application’s OIDC client identifier.
Exact match to a pre‑registered redirect URI for your client.
Must be
code.Space‑delimited scopes. Must include
openid idv. Supported: openid, idv.Recommended to bind the ID Token to a client session.
Request a minimum Level of Assurance. Format:
loa:{level} where level is 1–5.
See Level of Assurance for details.Required when initiating a match-capable provider over OIDC. A JWT carrying the values you want compared against the authoritative source.The result is returned via the standard userinfo flow with
- Algorithm:
HS256, signed with yourclient_secret. - Payload claim:
match_data— an object whose keys are provider-native (seematchDatafield schema). - Other claims: standard JWT (
iat,exp,jti) and OAuth/OIDC params (client_id,redirect_uri,state,nonce,scope) may also be carried in the JWT; if present they take precedence over their query-string equivalents.
Decoded payload
verification_model: "match" — see Return Data Model.Behavior
- If successful, responds with
302 Foundto yourredirect_uriwithcodeandstatequery params. - On failure, redirects with
erroranderror_description(andstateif provided).

