> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/id-repository-v1.2.3.1.md).

# ID Repository v1.2.3.1

**Release Version:** ID Repository v1.2.3.1

**Release Type:** Patch Release

**Release Date:** 12th November, 2026

### Overview

This release addresses an issue in the [ID Repository](https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-issuance/id-repository.md) where anonymous profile data was stored as null in the database. The fix ensures that anonymous profile data is correctly populated in IDRepo, improving the reliability and consistency of anonymous profile data storage.

### Major Highlights/ Features

* **Anonymous Profile Data Fix:** Ensures anonymous profile data is correctly stored in IDRepo.
* **UIN History Data Fix:** Ensures UIN history data is correctly populated and maintained across biometric and document history tables during UIN creation, activation, and updates.

### Bug Fixes

| JIRA                                                                                                                                                        | Description                                                     |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| [MOSIP-45189](https://mosip.atlassian.net/browse/MOSIP-45189?xpis=eyJicmlkZ2UiOiJzbWFydExpbmtzIiwiaWQiOiIxNzkxODcxMTU1MDE1Iiwic291cmNlIjoiY29uZmx1ZW5jZSJ9) | Anonymous profile data is null in IDRepo database               |
| [issue-1712](https://github.com/mosip/id-repository/issues/1712)                                                                                            | UIN History Data Missing in biometric\_h and document\_h Tables |

### Repositories Released

| Repository    | Tags                                                             |
| ------------- | ---------------------------------------------------------------- |
| ID Repository | [v1.2.3.1](https://github.com/mosip/id-repository/tree/v1.2.3.1) |

### Compatible Platform/Module

The following table outlines the tested and certified compatibility of ID Repository v1.2.3.1 with other modules.

| Platform/ Module | Version                                                                             |
| ---------------- | ----------------------------------------------------------------------------------- |
| MOSIP            | [v1.2.0.2](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/1.2.0.2)       |
| eSignet          | [v1.4.1](https://docs.esignet.io/home/esignet/roadmap-and-releases/versions/v1.4.1) |

### Documentation

* [Feature Documentation - Anonymous Profiling Support](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/reporting/anonymous-profiling-support)
* [Feature Documentation - ID Repository](https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-issuance/id-repository)
* [QA Report](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/id-repository-v1.2.3.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.mosip.io/1.2.0/roadmap-and-releases/releases/id-repository-v1.2.3.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.
