OpenID Connect meets distributed Self-Sovereign Identities

Self-Sovereign Identity (SSI) emerged with the rise of blockchain technology. This paradigm focuses on user-centricity and strives to place the user in full control of the digital identity. It is a concept in the digital movement that only the user should own their identity data fully without intervention from outside administration. By using a Self-Sovereign Identity, the individual identity holders can control and create their credentials completely, without having to ask permission from a centralized authority or intermediary and give control over how their personal data is used and shared.

Verifiable Credentials (VCs) are the electronic equivalent of the physical credentials, such as: driving licenses, diplomas, passports, etc. Cryptographic signatures make verifiable credentials more trustworthy and secure than their physical counterparts.

The data model for verifiable credentials is a World Wide Web Consortium Recommendation, “Verifiable Credentials Data Model 1.0 – Expressing verifiable information on the Web” published 19 November 2019.”

Decentralized Identifiers (DIDs) are described as the linchpin of self-sovereign identity. So, they are a type of identifier that enables a verifiable, decentralized digital identity.

A DID identifies any subject (e.g., organization, data model, a person, etc.) that the controller of the DID decides that it identifies. These identifiers have been designed in such a way that the controller of a DID has control over it and can be decoupled from centralized registries, identity providers, or certificate authorities.

OpenID Connect (OIDC) is an authentication layer on top of the OAuth 2.0 authorization framework, which allows computing clients to verify the identity of an end-user based on the authentication performed by an authorization server, as well as to obtain basic profile information about the end-user in an interoperable and REST-like manner. In technical terms, OpenID Connect specifies a RESTful HTTP API, using JSON as a data format.”. The standard is controlled by the OpenID Foundation.

Codeb’s inbuilt Identity Server can act now as an OpenID Connect provider on top of its Self-Sovereign Identity System. OpenID provided by the CodeB Identity Server unifies the benefits of all the above mentioned technologies.

To create a user just go to: and follow the instructions.

Kindly contact us for some test credits as the are required to add claims!

Our OpenID Connect test system can be consumed via:

Also have a loot at: Use CodeB SSI as OIDC Identity Provider for NextCloud

A dummy consuming website has been created for testing on:


Our OpenID Connect platform works perfectly with the Microsoft Authentication Library (MSAL). We can also supply you with or C# sample source code if required. Just contact us.