Create an OIDC Verifier
Creates a new OIDC Credential Verifier on the tenant.
Once created, this OIDC Verifier is publicly available on its /.well-known/openid-configuration
path. The Authorization header is not required as it is intended for OIDC Client applications to resolve.
Analytics Events
Roles
/ext/oidc/v1/verifiers
In: header
The verifier payload
Specifies the DID where the verifiable presentation will be sent to.
References the unique identifier of a Presentation Request Template that will be used by this verifier to create presentation requests.
uuid
As part of verifying a credential, the OIDC client initiates the request expecting a standard OIDC ID Token. However, as the digital wallet provides the credential in JSON-LD terms, it is required to map JSON-LD claims to OpenID Connect terms.
- Currently the platform only supports
schema.org
for data vocabularies. - Make sure to use
http://
and nothttps://
when entering jsonLdFqn values for schema.org. Otherwise you may not get the claims returned in your ID Token.
When set to true
, the generated id_token
will include the original presentation from the wallet.
Response Body
curl -X POST "https://example.vii.au01.mattr.global/ext/oidc/v1/verifiers" \ -H "Content-Type: application/json" \ -d '{ "verifierDid": "did:key:z6MkrYVmyqSA93o4B1GwERM8kaQDMAUKAFV2TC3weQKeg9Gq", "presentationTemplateId": "364b6a1b-3600-4927-a6ac-4d66aa6bbac3", "claimMappings": [ { "jsonLdFqn": "http://schema.org/alumniOf", "oidcClaim": "alumni_of" } ], "includePresentation": true }'
{
"id": "41458e5a-9092-40b7-9a26-d4eb43c5792f",
"verifierDid": "did:key:z6MkrYVmyqSA93o4B1GwERM8kaQDMAUKAFV2TC3weQKeg9Gq",
"presentationTemplateId": "364b6a1b-3600-4927-a6ac-4d66aa6bbac3",
"claimMappings": [
{
"jsonLdFqn": "http://schema.org/alumniOf",
"oidcClaim": "alumni_of"
}
],
"includePresentation": true
}
{
"code": "string",
"message": "string",
"details": [
{
"value": "string",
"msg": "Invalid value",
"param": "id",
"location": "body"
}
]
}
How would you rate this page?