Important: Please be informed that, beginning from December 2023, the Wallet Kit will no longer receive new features. Furthermore, the Wallet Kit is planned for discontinuation by the end of Q3 2024.
However, all functionalities offered by the Wallet Kit are now integrated into our new libraries, APIs, and apps in the walt.id identity repo. Giving you more modularity, flexibility and ease-of-use to build end-to-end digital identity and wallet solutions.
For any clarification or questions, feel free to contact us.
- REST Api - Use the functionality of the Wallet Kit via an REST api.
- Maven/Gradle Dependency - Use the functions of the Wallet Kit in a Kotlin/Java project.
The Wallet Kit on its own gives you, the backend infrastructure to build a custom wallet solution. However, in conjunction with our pre-build frontend components, you can even have a full solution. Get started with the full solution, using:
Checkout the Official Documentation, to find out more.
It is the API and backend business logic for the walt.id web wallet. Additionally, it includes a reference implementation of a Verifier and Issuer Portal backend.
- User management
- Authorization is currently mocked and not production ready
- User-context switching and user-specific encapsulated data storage
- Basic user data management
- List dids
- List credentials
- Verifiable Credential and Presentation exchange
- Support for credential presentation exchange based on OIDC-SIOPv2 spec
- Wallet configuration
- Possibility to configure list of supported wallets (defaults to walt.id web wallet)
- Presentation exchange
- Support for presentation exchange based on OIDC-SIOPv2 spec
- Wallet configuration
- Possibility to configure list of supported wallets (defaults to walt.id web wallet)
- Verifiable credential issuance
- Support for issuing verifiable credentials to the web wallet, based on OIDC-SIOPv2 spec
- Connect and get the latest updates: Discord | Newsletter | YouTube | Twitter
- Get help, request features and report bugs: GitHub Discussions
- Web Wallet - The frontend solution for holders
- Verifier Portal - The frontend solution for verifiers
- Issuer Portal - The frontend solution for issuers
The snap-shot version of this repository is automatically deployed for testing purpose. Feel free to access the test system at the following endpoints:
Configuration and data are kept in sub folders of the data root:
config/data/
Data root is by default the current working directory.
It can be overridden by specifying the environment variable:
WALTID_DATA_ROOT
config/verifier-config.json
{
"verifierUiUrl": "http://localhost:4000", # URL of verifier portal UI
"verifierApiUrl": "http://localhost:8080/verifier-api", # URL of verifier portal API
"wallets": { # wallet configuration
"walt.id": { # wallet configuration key
"id": "walt.id", # wallet ID
"url": "http://localhost:3000", # URL of wallet UI
"presentPath": "CredentialRequest", # URL subpath for a credential presentation request
"receivePath" : "ReceiveCredential/", # URL subpath for a credential issuance request
"description": "walt.id web wallet" # Wallet description
}
}
}
config/issuer-config.json
{
"issuerUiUrl": "http://localhost:5000", # URL of issuer portal UI
"issuerApiUrl": "http://localhost:8080/issuer-api", # URL of issuer portal API (needs to be accessible from the walletkit)
"wallets": { # wallet configuration
"walt.id": { # wallet configuration key
"id": "walt.id", # wallet ID
"url": "http://localhost:3000", # URL of wallet UI
"presentPath": "CredentialRequest", # URL subpath for a credential presentation request
"receivePath" : "ReceiveCredential/", # URL subpath for a credential issuance request
"description": "walt.id web wallet" # Wallet description
}
}
}
User data (dids, keys, credentials) are currently stored under
data/<user@email.com>
It is planned to allow users to define their own storage preferences, in the future.
The APIs are launched on port 8080.
A swagger documentation is available under
/api/swagger
Wallet API is available under the context path /api/
Verifier portal API is available under the context path /verifier-api/
Issuer portal API is available under the context path /issuer-api/
Gradle or Docker can be used to build this project independently. Once running, one can access the Swagger API at http://localhost:8080/api/swagger
gradle build
unzip package under build/distributions and switch into the new folder. Copy config-files service-matrix.properties and signatory.conf from the root folder and run the bash-script:
./bin/waltid-walletkit
To run the backend you will execute:
waltid-walletkit run
To have issuers, you will have to execute:
waltid-walletkit --init-issuer
docker build -t waltid/walletkit .
docker run -it -p 8080:8080 waltid/walletkit
To spawn the backend together with the wallet frontend, the issuer- and the verifier-portal, one can make use of the docker-compose configuration located in folder:
./docker/
In order to simply run everything, enter:
docker-compose up
This configuration will publish the following endpoints by default:
- web wallet on [HOSTNAME]:8080
- wallet frontend: http://[HOSTNAME]:8080/
- wallet API: http://[HOSTNAME]:8080/api/
- verifier portal on [HOSTNAME]:8081
- verifier frontend: http://[HOSTNAME]:8081/
- verifier API: http://[HOSTNAME]:8081/verifier-api/
- issuer portal on [HOSTNAME]:8082
- issuer frontend: http://[HOSTNAME]:8082/
- issuer API: http://[HOSTNAME]:8082/issuer-api/
Note
[HOSTNAME] is your local computer name. Using localhost, not all features will work correctly.
Visit the ./docker. folder for adjusting the system config in the following files
- docker-compose.yaml - Docker config for launching containers, volumes & networking
- ingress.conf - Routing config
- config/verifier-config.json - verifier portal configuration
- config/issuer-config.json - issuer portal configuration
By specifying the optional startup parameter --init-issuer the walletkit can be initialized as issuer-backend in line with the EBSI/ESSIF ecosystem. Note that this is for demo-purpose only.
cd docker
docker pull waltid/walletkit
docker run -it -v $PWD:/waltid-walletkit/data-root -e WALTID_DATA_ROOT=./data-root waltid/walletkit --init-issuer
# For the DID-method enter: "ebsi"
# For the bearer token copy/paste the value from: https://app.preprod.ebsi.eu/users-onboarding
The initialization routine will output the DID, which it registered on the EBSI/ESSIF ecosystem.
- Self-Issued OpenID Provider v2
- OpenID Connect for Verifiable Presentations
- OpenID Connect for Verifiable Credential Issuance
- EBSI Wallet Conformance
- Verifiable Credentials Data Model 1.0
- Decentralized Identifiers (DIDs) v1.0
- DID Method Rubric
- did:web Decentralized Identifier Method Specification
- The did:key Method v0.7
Licensed under the Apache License, Version 2.0