0.3.1 - Key Pair Access Policies

Key Pair Access Policies

Ability to guard the key pairs used in the SDK with local authentication such as biometrics or passcodes.

0.3.0 - OID4VP initial support

Version of OID4VP Supported: 1.0.0

Client ID verification

Verification method	Prefix	Supported
Pre-registered (default)	N/A (None)	[x]
X509 SAN DNS	x509_san_dns	[ ]
X509 HASH	x509_hash	[ ]
DID	decentralized_identifier	[ ]
Verifier Attestation	verifier_attestation	[ ]
OpenID Federation	openid_federation	[ ]
redirect_uri	redirect_uri	[ ]

Credential Query

We only support DCQL (Digital Credential Query Lanaguage) queries in the authorization requests.

Tip

We support adding manadatory credentials for the org.iso.18013.5.1.mDL docType so if no claims are queried all claims marked as mandatory in the standard are 'added' / used as the query.

Response modes

Response mode	Supported	Description
direct_post	[x]	The Verifiable Presentation (VP) is sent in the body of a POST request to the response_uri.
direct_post.jwt	[x]	The VP is sent as a JWE in the body of a POST request to the response_uri.
dc_api	[ ]	The wallet responds via the digital credentials API without encrypting the response.
dc_api.jwt	[ ]	Same as dc_api but the wallet responds with a JWE.
query	[ ]	The VP is sent as a vp_token query parameter. The state is also returned for CSRF protection.
fragment	[ ]	The VP is sent as a vp_token fragment parameter. The state is also returned for CSRF protection.

Release 0.2.0

Release 0.2.0

What's Changed

• Added OID4VCI Draft 13 support for MDoc credentials.

Full Changelog: 0.1.1...0.2.0

Release 0.1.1

Release v0.1.1

Adds support for 'skip' verification method.