The SSI Console leverages the SSI Service API to simplify credential issuance and verification in an easy to manage web interface.
- Create and manage Decentralized Identifiers (DIDs)
- Issue and Verify Verifiable Credentials (VCs)
Verify that both
docker-compose commands are available:
Clone and Run SSI Console
git clone https://github.com/TBD54566975/ssi-console.git
Open localhost:3000 in a browser and follow the guide below for all actions you can take from the homepage.
Create a Decentralized Identifier (DID)
Upon installation, a DID will be created by default, but you can follow the steps below to create one for yourself.
3. Set DID Method
There are three different DID methods to choose from:
Key. The DID
Key method is a good method for testing purposes so let's select that for now.
4. Set keyType and options
Try sample input and then submit.
Learn more about what you can add to this field.
Create a Verifiable Credential (VC)
3. Add name and description
Feel free to use the default placeholders or describe your new VC. Then click
4. Prep VC Schema
New data set.
Try sample inputand fill in the VC subject's first and last name.
5. Set Input Descriptors (optional)
Try sample input and leave the default JSON for now, and click
This field populates the presentation_definition field of the
credential_manifest. When a subject, for example an employee, applies for this credential, they will be required to present any credentials defined in this field. Here, we are asking for a credential with the subject's
firstName and a credential with the subject's
path field defines which path we can expect to find these values in the subject's provided credentials.
6. Set issuer information
Fill in an issuer name (company name) for the employment verification, then click
A new VC has now been created.
Next Steps for VCs
Send an Application
Share the Application URL with subjects, employees in this case, to apply for their new employment verifiable credential.
The credential applicant will need to submit a credential application as a JSON Web Token (JWT). Once they submit the JWT, the application will become available for review in the dashboard, under Credentials > Applications.
Learn more about applications.
Issue a VC
Issueon a created VC.
Subject DID: Add your employee's DID.
Subject Data: Fill in your employee's first and last name.
- Decide whether you want this DID to be
- Set an
expirationdate if you want it to expire.
Issuer DID: Choose one of the employers' DIDs.
Verify a Credential
We use presentation definitions to create submission links, through which subjects can submit their relevant credentials for verification.
3. Name your presentation definition
4. Set Purpose
Include the purpose of your presentation definition. It should answer: why are you requesting this credential?
5. Set Input Constraints
Try sample input again and leave the default added JSON for now.
It will look for credentials to verify the
6. Set verifier
Choose your verifier DID from the dropdown. You can use the same Ion DID you used to create the VC.
Applications: When an employee applies for a credential with your applicaton link, and you as the employeer will see that application here for the you (the employer) to approve or decline. If you approve their application you would then issue their employment credential.
Submissions: When an employer asks a job applicant to submit an education VC for example before accepting their role.