Skip to content

OpenID Credential Exchange Service


Trinsic provides an OpenID Connect ("OIDC") service which enables verifiers to request credentials from a user's cloud wallet in a simple and secure way.

This service does not require the use of Trinsic's SDKs in the user's browser, and is therefore lightweight and easy to integrate.

Credential Issuance

Currently, Trinsic's OpenID Connect service only enables the sharing of a credential between holder and verifier. We plan to support issuance through this service at a later date.

In the meantime, use the [InsertItem](../services/ or [Send](../services/ methods to store credentials in a holder's wallet.


OpenID Connect Protocol

Because this is an OpenID Connect service, any compliant library may be used -- as long as it enables you to specify additional custom query parameters on the initial outbound URL.

OIDC Flow Implementation

The specifics of the OpenID Connect protocol -- and how to implement it -- are out of scope for this documentation.

If you would like to see an example implementation of a verification flow against this service, see the sample below.


Configure your OIDC library with the following parameters:

Parameter Description
General Parameters
response_type code
scope openid
client_id Any string which uniquely represents your client application
redirect_uri The URI your user should be redirected to once they have completed (or canceled) the flow
nonce (Optional) Random nonce value that will be used to bind the generated presentation to the issued token. If not specified, one will be randomly generated. Use this to prevent presentation replays.
Trinsic-Specific Parameters
trinsic:ecosystem ID of ecosystem user wallet resides in
trinsic:schema (Optional) Comma-separated listed of Schema URLs. Only credentials which match one of these schemas will be returned.
trinsic:issuer (Optional) Comma-separated list of Issuer DIDs. Only credentials issued by one of these issuers will be returned.
trinsic:egf (Optional) Comma-separated list of Entity Governance Framework IDs. Only credentials bound to one of these EGF IDs will be returned.
trinsic:mode (Optional) Can be redirect (default), popup, or silent.
trinsic:verification_template_id (Optional) ID of the verification template that will be used to perform the verifications. Format: urn:template:<ecosystem_name>:<verification_template_name>

Presentation Replays and ID Tokens

In order to prevent verifiable presentation replays, always specify the nonce parameter in the initial call to the authorization endpoint. This will ensure that the generated presentation and the ID token match the current request.

Response Data

Once the user has returned to your redirect URL, exchange the authorization code (added to your redirect URI as a query parameter named code) for an identity token using your OIDC library.

You will receive a JSON object of the following form:

Response JSON
    "id_token": "{JWT containing same data as vp_token}",
        "id":"{UUID of Holder Wallet}",
        "issuanceDate":"{Issue date of credential}",
        "issuer":"{DID of Issuer}",

Credential Format

Note that the above data has been modified for brevity.

The `@context` and `type` arrays will contain additional entries which are specific to the credential.

Verify the Received Proof

vp_token is a Verifiable Proof; before making use of its data, you must verify it.

This proof can be verified with any library that supports VC verifications for BBS+ signatures. It can also be verified using Trinsic's SDK; this is as simple as passing the proof to the VerifyProof call.

If you specified a nonce in the authorization request, always verify that the nonce claim in the JWT ID token matches the similarly named value in the _vp_token document. You may find the nonce in the _vp_token.proof.nonce path in the JSON structure. Note that the value in this proof may be specified in base64 format, so you may need to reformat your nonce before comparing. If you specified the nonce as base64 in the request, the two values should match with direct string comparison.

Always Verify

It may be tempting to simply take the data in vp_token and act upon it without first verifying the proof.

**Always verify the proof** before making use of its data.

Without verification, the received proof is of no more value than an unsubstantiated claim made by your user.

Displaying Linked Data in Credentials

SDK Only

The following section presently only applies when using our SDK to create a Template; our Dashboard does not yet support the ability to specify field annotations.

Some credential template fields may be intended for URLs which resolve to images or any other data which cannot be directly embedded in a credential. For example, you may wish to include a URL to an image of a physical credential in its digital representation.

By default, these will display to the holders in the OIDC flow as simple text fields containing the raw URL. However, the template can be configured to display these URLs as either inline embedded images, or convenient links to download the linked data.

When creating or updating a Template:

  • Choose the URI type for any Fields which are intended to contain URIs.
  • Configure the UriData object on the Field
    • Set the RenderMethod property
      • If the field is intended to contain an image, use the value INLINE_IMAGE.
      • Otherwise, use LINK for a clickable link, or TEXT to display the URI in raw form.
    • Set the MimeType property
      • Use the value image if the field is intended to contain a link to an image
      • Otherwise, the value should be the expected MIME Type of the data
        • If you are unsure, use application/octet-stream as a catch-all


We've prepared a sample demonstrating client-side OIDC Verification.

  • Sample Source

    The source for this sample is available on GitHub

OIDC Libraries

Libraries exist enabling OIDC functionality for all major languages.

The OpenID Connect website lists a number of certified libraries; we've included links to some of these below.