> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-certify/releases/version-0.13.1.md).

# Version 0.13.1

**Release Version**: v0.13.1

**Release Type:** Developer Release

**Release Date:** 5th December, 2025

### **Overview** <a href="#overview" id="overview"></a>

Inji Certify v0.13.1 release includes an automation bug fix required to support the new features introduced in version 0.13.0.

### **Major Highlights / Features**

* Corrected the certificate path in the automation scripts to ensure the appropriate certificates are used for generating biometric data during prerequisite creation for MOSIP ID use cases.

### Bug Fixes <a href="#bug-fixes" id="bug-fixes"></a>

Here below is the bug which has been addressed as part of this release.

| JIRA                                                              | Description                                        |
| ----------------------------------------------------------------- | -------------------------------------------------- |
| [INJICERT-1279](https://mosip.atlassian.net/browse/INJICERT-1279) | Authenticate user API failing with test automation |

### Repository Released <a href="#repository-released" id="repository-released"></a>

| Repository   | Version                                                       |
| ------------ | ------------------------------------------------------------- |
| inji-certify | [v0.13.1](https://github.com/mosip/inji-certify/tree/v0.13.1) |

### Known Issues <a href="#known-issues" id="known-issues"></a>

Below is the list of known issue(s) related to the release v0.13.1. To access all the known issues related to Inji Certify please refer [here](https://mosip.atlassian.net/issues/?filter=16603).

| JIRA                                                             | Description                               |
| ---------------------------------------------------------------- | ----------------------------------------- |
| [INJICERT-43526](https://mosip.atlassian.net/browse/MOSIP-43526) | Hardcoded domain in IDA automation script |

### Compatible Modules <a href="#compatible-modules" id="compatible-modules"></a>

| Repositories          | Version                                                                         |
| --------------------- | ------------------------------------------------------------------------------- |
| eSignet               | [v1.6.2](https://github.com/mosip/esignet/tree/v1.6.2)                          |
| IDA                   | [1.2.1.0](https://github.com/mosip/id-authentication/tree/v1.2.1.0)             |
| Sunbird C             | [v2.0.0](https://github.com/Sunbird-RC/sunbird-rc-core/releases/tag/v2.0.0-rc3) |
| esigent-mock-services | [v0.11.2](https://github.com/mosip/esignet-mock-services/tree/v0.11.2)          |
| commons               | [v1.3.0-beta.3](https://github.com/mosip/commons/tree/v1.3.0-beta.3)            |
| key manager           | [v1.3.0-beta.5](https://github.com/mosip/keymanager/tree/v1.3.0-beta.5)         |
| mimoto                | [v0.18.1](https://github.com/mosip/mimoto/tree/v0.18.1)                         |
| inji-web              | [v0.13.1](https://github.com/mosip/inji-web/tree/v0.13.1)                       |

### Documentation <a href="#documentation" id="documentation"></a>

* [Feature Documentation](https://docs.mosip.io/inji/inji-certify/functional-overview/features)
* [Local Setup](https://docs.mosip.io/inji/inji-certify/build-and-deploy/local-setup)
* [API Documentation](https://mosip.stoplight.io/docs/inji-certify/25f435617408e-inji-certify)
* [Test Report](/inji-certify/releases/version-0.13.1/test-report.md)


---

# 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://docs.inji.io/inji-certify/releases/version-0.13.1.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.
