Create OIDC client
Creates an OpenID Connect client of the Passwordless Login extension. Your identity and access management system (for example Keycloak or Auth0) or your application uses the client to log people in with the EUDI Wallet: the authorisation page shows a QR code, the person presents the credentials of the presentation definition, and the tokens hold a sub that identifies the person.
Choose how the provider resolves the sub: with identityMatchingAttributes (a claim of the presentation) or with your own callbackURI. Give exactly one.
The answer holds clientId and clientSecret. Configure them in your system, with the discovery URL of the provider. The Passwordless Login (oidc) extension must be on.
Authorizations
AuthorizationstringheaderrequiredYour API key with the prefix
ApiKey:ApiKey <your-api-key>. Get an API key.Scope:
extensions:create
Body
presentationDefinition Id stringrequiredThe presentation definition that the login page asks the EUDI Wallet to answer. It must not belong to another client. It must sign with an X.509 key that it names (
cryptographicKeyFormatx509andcryptographicKeyIdentifier) and use the client ID schemex509_hash. It can have the transaction data templatelogin_risk_transaction_non_ts12orlogin_risk_transaction, but no credential that comes with its own transaction data (the TS12 payment wallet attestation, software statement, QESAC and SCA credentials): such a definition is for another purpose than login. It must not ask for a PID (an SD-JWT VC type that starts withurn:eudi:pid:, the mdoc typeeu.europa.ec.eudi.pid.1or the old typeurn:eu.europa.ec.eudi:pid:1): the PID Rulebook does not allow a PID to sign transaction data.namestringrequiredThe name of the client.
redirectURIs string[]The redirect URIs of your identity and access management system or application. Each is a URL with scheme and host, without fragment. The
redirect_uriof an authorisation request must match one of them exactly.allowedOrigins string[]The web origins of your application (scheme, host and optional port, no path).
identityMatching Attributes objectThe claim that becomes the
sub, for each credential of the DCQL query of the presentation definition. The key is thevct(SD-JWT VC), thedoctype(mdoc) or atype(W3C VC) of the credential, the value is the dot-separated path of the claim. Both must exist in the DCQL query. Do not send it withcallbackURI.callbackURI stringAn HTTPS endpoint of yours that resolves the
sub. At the token request, the provider sends it the presentations as a JSON array in a POST request, withAuthorization: Bearer <callbackSecret>and anX-IGrant-Signatureheader. It must answer200within 30 seconds with a JSON object that holdssub. Do not send it withidentityMatchingAttributes.callbackSecret stringThe secret that the provider sends to
callbackURIas a bearer token, and the key of theX-IGrant-SignatureHMAC. Mandatory withcallbackURI.transactionData Action stringThe text that the EUDI Wallet shows about the login, for example
Log in to your online bank account, at most 140 characters. Mandatory when the presentation definition has a transaction data template, refused when it has none.At most 140 characters.
Example:
"Log in to your online bank account"
Response
The client is created.
Headers
Cache-Control stringThe answer holds a secret. Do not cache it.
Example:
"no-store"
clientId stringThe client ID.
clientSecret stringThe client secret. Keep it on your server. Read the client to get it again.