O02 - Support multiple VC Schemas
Sequence | Objective Detail | Test Procedure |
---|---|---|
O02 | Confirm that the Innovation allows users to create multiple verifiable credential schemas. | Use different templates of data schema, and create a custom data schema to be embedded in a digital credential. |
Assumptions & Acceptance Criteria
- The issuer provides an API to create new VC schemas based on a pool of existing claim fields
- The issuer provides an administrative UI to create new VC schemas based on a pool of existing claim fields
Testing Guidance
Create new VC schema using UI
-
Log into the Issuer Portal at https://admin.blueprintissuer.com
astuceDefault admin credentials are:
Login: adminlevel4@blueprintissuer.com
Password: adminpassword -
Navigate to Settings -> Claim Ensembles
-
Start creating a new Claim Ensemble by clicking the call to action
-
Enter in the required fields
Example Payload
name:
Driver's License
category:default
fields:["familyName", "givenName", "gender", "birthDate", "height"]
astuceFor testing purposes, always use
default
for the categoryinfoAvailable list of Claim fields are based on database schema for profiles. Learn more (TBD)
Create new VC schema using API
-
Choose how to authenticate to the API (e.g. token or api key)
-
Call the
POST /admin/claim-ensemble
api route with the required PayloadExample 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