O01 - Issue and verify credentials from multiple DID methods

Sequence	Objective Detail	Test Procedure
O01	Confirm that the Innovation is able to issue and verify credentials from multiple platforms with multiple Decentralized Identity Document (“DID”) methods.	The test will assert that the Innovation supports at least two Decentralized Identity Document (“DID”) methods

Assumptions & Acceptance Criteria

• The issuer is able to issue credentials using at least 2 DID methods (web, jwk, key)
• The verifier is able to verify credentials issued using at least 2 DID methods (web, jwk, key)

Testing Guidance

Issue credentials using UI

1. Log into the Issuer Portal at https://admin.blueprintissuer.com

   astuce

   Default admin credentials are:
   Login: adminlevel4@blueprintissuer.com
   Password: adminpassword

2. Navigate to Settings -> Claim Ensembles

3. Start creating a new Claim Ensemble by clicking the call to action

4. Enter in the required fields

   Example Payload

   name: Driver's License
   category: default
   fields: ["familyName", "givenName", "gender", "birthDate", "height"]

   astuce

   For testing purposes, always use default for the category

   info

   Available list of Claim fields are based on database schema for profiles. Learn more (TBD)

Create new VC schema using API

1. Choose how to authenticate to the API (e.g. token or api key)

2. Call the POST /admin/claim-ensemble api route with the required Payload

   Example payload

   {
     "name": "Proof of Age",
     "category": "default",
     "fields": [
       "birthDateField",
       "givenNameField",
       "familyNameField",
       "genderField"
     ]
   }

   Example response (201 created)

   {
     "id": "08e7a65c-354a-4865-bf4e-4740a540d905",
     "name": "Proof of Age",
     "category": "default"
   }

Additional Considerations

• The issuer also provides deletion and modification endpoints, but these also bring up edge cases that require further clarification
• Deletion and modification of VC schemas are disabled in the administrative UI for the reason above