@mattrglobal/verifier-sdk-web 2.0.0-preview-digital-credential-api.1 → 2.0.0-preview-digital-credential-api.3

package/README.md

@@ -12,6 +12,7 @@
     - [Web project with an existing bundler set up](#web-project-with-an-existing-bundler-set-up)
     - [Loading directly from script tag](#loading-directly-from-script-tag)
 - [Usage](#usage)
+  - [Support for Digital Credential API (Tech Preview)](#support-for-digital-credential-api-tech-preview)
   - [Initialise the SDK](#initialise-the-sdk)
   - [Prepare a credential query](#prepare-a-credential-query)
   - [Generate challenge](#generate-challenge)
@@ -61,7 +62,7 @@ to any of our SDKs.
 1. Install dependencies via yarn:
 
 ```bash
-yarn add @mattrglobal/verifier-sdk-web
+yarn add @mattrglobal/verifier-sdk-web@2.0.0-preview-digital-credential-api.2
 ```
 
 2. Import the sdk module in your code:
@@ -77,11 +78,9 @@ MATTRVerifierSDK.initialise(...);
 1. Load the following script tag from your web page:
 
 ```html
-<script src="https://cdn.mattr.global/js/verifier-sdk-web/1.0/verifier-js.production.js"></script>
+<script src="https://cdn.mattr.global/js/verifier-sdk-web/2.0.0-preview-digital-credential-api.2/verifier-js.production.js"></script>
 ```
 
-> This script will automatically pick up any SDK patch updates. You can lock your implementation to a specific patch version by replacing 1.0 with the specific version (e.g. https://cdn.mattr.global/js/verifier-sdk-web/1.0.1/verifier-js.production.js).
-
 2. Access SDK functions via global `MATTRVerifierSDK` object.
 
 ```javascript
@@ -100,11 +99,26 @@ The SDK can make a request to create a presentation session with a configured MA
 * Define what wallets can be used to respond to the verification request.
 * Configure the URI the user will be redirected to when the verification workflow is completed (only required for same-device flows).
 
+## Support for Digital Credential API (Tech Preview)
+
+This SDK supports the experimental Web Platform Digital Credential API and will automatically attempt to use the Digital Credential API (ahead of executing the request based on OpenID4VP as per ISO 18013-7) when the following conditions are met:
+- The SDK detects the Digital Credential API is available in the current web browser.
+- The feature has been enabled when the SDK was [initialised]((#initialise-the-sdk).
+  
 ## Initialise the SDK
 
 You must initialise the SDK before you can use any of its functions and methods.
 
-When initialising the SDK, you must provide the URL of the MATTR VII verifier tenant.
+```javascript
+MATTRVerifierSDK.initialise({
+  apiBaseUrl: "{tenant_url}", // provide the URL of the MATTR VII verifier tenant.
+  /** 
+   * Configurations when Digital Credential Api is available 
+   **/
+  enableDigitalCredentialsApiSameDeviceFlow: true, // indicates whether the SDK will use the Digital Credential API in same-device flows.
+  enableDigitalCredentialsApiCrossDeviceFlow: false, // indicates whether the SDK will use the Digital Credential API in cross-device flows.
+});
+```
 
 ## Prepare a credential query
 
@@ -159,9 +173,11 @@ You can define an identifier of a specific wallet you want to invoke with this v
 * If an identifier is provided and does not match the `id` of any of the objects in the `walletProviders array`, the request will fail.
 * If an identifier is not provided, the verifier tenant will use `mdoc-openid4vp://` (default OID4VP scheme) to invoke any wallet.
 
+**Note** that if the SDK request credentials via the Digital Credential API, the mobile operating system will prompt the user to make a selection of which credential from which wallet it would like to respond to the request with.
+
 ## Configure redirectUri
 
-When using the same-device presentation flow, the SDK must define what URI to redirect the user to once they complete the verification workflow in their wallet app. This can be any URI (including custom URI schemes), and must match one of the values defined in the [`redirectUris` array](https://learn.mattr.global/latest/tag/mDocs-verification#operation/putVerifierConfiguration!path=redirectUris&t=request) in the MATTR VII tenant's verifier configuration.
+When using the same-device presentation flow with OpenID4VP (ISO 18013-7) e.g instead of using the Digital Credential API, the SDK must define what URI to redirect the user to once they complete the verification workflow in their wallet app. This can be any URI (including custom URI schemes), and must match one of the values defined in the [`redirectUris` array](https://learn.mattr.global/latest/tag/mDocs-verification#operation/putVerifierConfiguration!path=redirectUris&t=request) in the MATTR VII tenant's verifier configuration.
 
 # Request credentials examples
 
@@ -169,7 +185,7 @@ When using the same-device presentation flow, the SDK must define what URI to re
 
 ```javascript
 MATTRVerifierSDK.initialise({ apiBaseUrl }); // Initialise the SDK
-const result = await MATTRVerifierSDK.requestCredentials({
+const requestCredentialsResult = await MATTRVerifierSDK.requestCredentials({
   credentialQuery: [credentialQuery], // Define what credential query to use
   challenge: MATTRVerifierSDK.utils.generateChallenge(), // Pass a unique challenge
   walletProviderId, // Define the wallet identifier
@@ -183,6 +199,17 @@ const result = await MATTRVerifierSDK.requestCredentials({
     },
   },
 });
+
+// Check result when it's available in the return value
+if (requestCredentialsResult.isOk() && "result" in requestCredentialsResult.value) { 
+  console.info("<<< MATTRVerifierSDK.requestCredentials result",result.value.result);
+}
+
+// Check result also in your page of redirect_uri
+window.addEventListener("load", async () => {
+  MATTRVerifierSDK.initialise({ apiBaseUrl });
+  const result = await MATTRVerifierSDK.handleRedirectCallback();
+});
 ```
 * `apiBaseUrl` : Replace with the [`tenant_url`](https://learn.mattr.global/docs/security/authentication) of your MATTR VII verifier tenant.
 * `credentialQuery`: The credential query to be used in the request.
@@ -196,7 +223,7 @@ const result = await MATTRVerifierSDK.requestCredentials({
 
 ```javascript
 MATTRVerifierSDK.initialise({ apiBaseUrl });
-const result = await MATTRVerifierSDK.requestCredentials({
+const requestCredentialsResult = await MATTRVerifierSDK.requestCredentials({
   credentialQuery: [credentialQuery],
   challenge: MATTRVerifierSDK.utils.generateChallenge(),
   redirectUri,
@@ -204,7 +231,12 @@ const result = await MATTRVerifierSDK.requestCredentials({
   mode: "sameDevice",
 });
 
-// result can be retrieved on redirect uri page. for example
+// Check result when it's available in the return value
+if (requestCredentialsResult.isOk() && "result" in requestCredentialsResult.value) { 
+  console.info("<<< MATTRVerifierSDK.requestCredentials result",result.value.result);
+}
+
+// Check result also in your page of redirect_uri
 window.addEventListener("load", async () => {
   MATTRVerifierSDK.initialise({ apiBaseUrl });
   const result = await MATTRVerifierSDK.handleRedirectCallback();
@@ -219,7 +251,7 @@ window.addEventListener("load", async () => {
 
 ```javascript
 MATTRVerifierSDK.initialise({ apiBaseUrl });
-const result = await MATTRVerifierSDK.requestCredentials({
+const requestCredentialsResult = await MATTRVerifierSDK.requestCredentials({
   credentialQuery: [credentialQuery],
   challenge: MATTRVerifierSDK.utils.generateChallenge(),
   walletProviderId,
@@ -233,6 +265,11 @@ const result = await MATTRVerifierSDK.requestCredentials({
     },
   },
 });
+
+// Check result when it's available in the return value
+if (requestCredentialsResult.isOk() && "result" in requestCredentialsResult.value) { 
+  console.info("<<< MATTRVerifierSDK.requestCredentials result",result.value.result);
+}
 ```
 
 * `mode`: When set to `crossDevice`, the SDK will only support cross-device flow in this verification workflow.

package/dist/lib/verifier-js-no-deps.cjs.js

@@ -1,5 +1,5 @@
 /*!
- * Copyright 2024 - MATTR Limited
+ * Copyright 2025 - MATTR Limited
  * All rights reserved
  * Confidential and proprietary
  *
@@ -7,8 +7,8 @@
  * Do Not Translate or Localize
  *
  * Bundle of @mattrglobal/verifier-sdk-web
- * Generated: 2024-10-21
- * Version: 2.0.0-preview-digital-credential-api.1
+ * Generated: 2025-02-18
+ * Version: 2.0.0-preview-digital-credential-api.3
  * Dependencies:
  */
 
@@ -394,11 +394,13 @@ const isDigitalCredentialsApiSupported = () => {
     }
 };
 
-const createDigitalCredentialsApiSession = async ({credentialQuery: credentialQuery, challenge: challenge, apiBaseUrl: apiBaseUrl}) => {
-    const postData = {
+const createDigitalCredentialsApiSession = async ({credentialQuery: credentialQuery, challenge: challenge, apiBaseUrl: apiBaseUrl, protocol: protocol}) => {
+    const postData = Object.assign({
         credentialQuery: credentialQuery,
         challenge: challenge
-    };
+    }, protocol && {
+        protocol: protocol
+    });
     const responseResult = await safeFetch(`${apiBaseUrl}/v2/presentations/sessions/browserApi/request`, {
         method: "POST",
         headers: {
@@ -633,7 +635,7 @@ var SameDeviceRequestCredentialsErrorMessage;
 
 const requestCredentialsDigitalCredentialsApi = async options => {
     const {challenge: challenge, credentialQuery: credentialQuery, initialiseOptions: initialiseOptions} = options;
-    const {apiBaseUrl: apiBaseUrl} = initialiseOptions;
+    const {apiBaseUrl: apiBaseUrl, digitalCredentialsApiProtocol: digitalCredentialsApiProtocol} = initialiseOptions;
     window.localStorage.setItem(LocalStorageKey.challenge, challenge);
     const storedChallenge = window.localStorage.getItem(LocalStorageKey.challenge);
     if (!storedChallenge) {
@@ -645,7 +647,8 @@ const requestCredentialsDigitalCredentialsApi = async options => {
     const createSessionResult = await createDigitalCredentialsApiSession({
         credentialQuery: credentialQuery,
         challenge: storedChallenge,
-        apiBaseUrl: apiBaseUrl
+        apiBaseUrl: apiBaseUrl,
+        protocol: digitalCredentialsApiProtocol
     });
     if (createSessionResult.isErr()) {
         return neverthrow.err({