Update #13

Hey friends,

In the past month, we made many updates and improvements in the identity library based on feedback and our goal to reach full feature parity with the old stack.

We integrated with Hashicorp Vault as one other option to secure your cryptographic keys. Published our first version of the walt.id CLI that brings digital identity features directly to your command line and many other features. Below, you find a full list of all the features that are now available and links to the respective documentation to get started.

Let’s dive in.

Identity Lib (v0.2.0)

Below are all features available through v0.2.0 of the identity lib. Checkout the full change log here. Want to learn more about the identity lib in general? Check out our intro video.


Hashicorp Vault integration

To ensure secure key management, utilize Hashicorp Vault in the issuer API to sign credentials. This integration also works with the core crypto library.

Get Started

Issuer setup

Quickly create a set of keys and DIDs based on various algorithms and DID methods used to sign credentials. It also works with Hashicorp Vault.

Get Started

DID web registry

The walt.id wallet-API and web-wallet now have a build in did:web registry. This makes any did:web created publicly resolvable without the burden to host an external host.

Get Started

Walt CLI

Access digital identity features, thereunder the creation of keys based on various algorithms, DID for different ecosystems and the creation and signing of Verifiable Credentials (W3C) in JWT and SD-JWT format directly from the command line. In this 0.2.0 release, we are publishing the first set of commands, which include the creation and import as well as export of keys.

Get Started

Custom OIDC Auth Module In Wallet-API

With this authentication strategy you can simply provide a valid JWT with a unique subject claim and the wallet-api will create or login a user to their wallet account. This way you can use your own authentication flows and just provide the result (valid JWT) to the walt.id system. To verify the JWT provided is coming from your auth server, you need to configure the relevant OIDC endpoints via a config.

Get Started



Feature List & Roadmap

Overview - product features today and upcoming


walt.id cloud waitlist

Sign up to get early access to our managed cloud service


PS: If you enjoy working with our tools, make sure to leave us a ⭐ on GitHub

Share an idea, ask a question, or chat?

Previous
Previous

Update #14

Next
Next

Update #12