> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/use/releases/credentialing.md).

# Credentialling

Release history for the Credentialling Services — Identity, Credential Schema, and Credential.

{% updates format="full" %}
{% update date="2026-08-10" tags="new-release,improvements" %}

## v2.1.0 — Standards-based wallet interoperability <a href="#v2.1.0" id="v2.1.0"></a>

{% content-ref url="/pages/TES2EBXdlACN3ZRtcLpk" %}
[v2.1.0 — Latest release](/use/releases/credentialing/v2.1.0-latest-release.md)
{% endcontent-ref %}

The first feature-bearing release in roughly two years. A new `oid4vc-service` makes the platform speak **OpenID4VCI 1.0** for issuance and **OpenID4VP 1.0/draft-23** for presentation, so any conformant wallet can receive a credential from a Sunbird RC deployment and present it back to a Sunbird RC verifier with no Sunbird-specific integration. Four credential formats are supported end-to-end, and W3C VC Data Model 2.0 lands alongside the existing 1.1 support.

Read the full v2.1.0 release notes
{% endupdate %}

{% update date="2026-05-21" tags="fixes" %}

## v2.0.3 — Security and stability <a href="#v2.0.3" id="v2.0.3"></a>

{% content-ref url="/pages/UNWhhtE0080IM5XQgASw" %}
[v2.0.3](/use/releases/credentialing/v2.0.3.md)
{% endcontent-ref %}

The platform-wide maintenance release, as it applied to the credentialling stack: Node dependency remediation across the Credential, Credential Schema and Identity services, the same hardened image baseline, and the repository-wide secrets cleanup.
{% endupdate %}

{% update date="2024-02-13" tags="improvements" %}

## v2.0.0-beta3 — Initial Credentialling Services release <a href="#v2.0.0-beta3" id="v2.0.0-beta3"></a>

{% content-ref url="/pages/9uzKKpxhOUrNnDpJqN01" %}
[v2.0.0](/use/releases/credentialing/v2.0.0.md)
{% endcontent-ref %}

The first release of the three-service credentialling stack — Identity Service, Credential Schema Service and Credential Service — which replaced the registry's older built-in signing and certificate path.
{% endupdate %}
{% endupdates %}

***

## Artifacts

All images are published on GHCR.

| Artifact                  | Image                                              |
| ------------------------- | -------------------------------------------------- |
| Identity Service          | `ghcr.io/sunbird-rc/sunbird-rc-identity-service`   |
| Credential Schema Service | `ghcr.io/sunbird-rc/sunbird-rc-credential-schema`  |
| Credential Service        | `ghcr.io/sunbird-rc/sunbird-rc-credential-service` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://rc.sunbird.org/use/releases/credentialing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
