> 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/1.2.1.0-beta.1-part-3.md).

# 1.2.1.0-beta.1 (Part 3)

**Release Version**: 1.2.1.0-beta.1

**Release Type:** Beta Release

**Release Date**: 18th March, 2025

#### **Overview**

This beta release introduces significant changes related to migration to Java 21 for improved compatibility and performance for a few of the modules.

For users who have already deployed MOSIP and intend to upgrade to Java 21, please refer [here ](https://docs.mosip.io/1.2.0/setup/upgrade/java-21-migration-guide)for a detailed, step-by-step process to ensure a seamless transition.

{% hint style="info" %}
**Note:** This component wise beta release will be part of the MOSIP Identity v1.2.1.0-beta.1 release.
{% endhint %}

**Major Areas of Work**

* Code Migration from JAVA 11 to JAVA 21

**Repository Released**

| Repositories         | Tags Released                                                                     |
| -------------------- | --------------------------------------------------------------------------------- |
| id-authentication    | [v1.3.0-beta.1](https://github.com/mosip/id-authentication/tree/v1.3.0-beta.1)    |
| id-repository        | [v1.3.0-beta.1](https://github.com/mosip/id-repository/tree/v1.3.0-beta.1)        |
| resident-services    | [v1.3.0-beta.1](https://github.com/mosip/resident-services/tree/v1.3.0-beta.1)    |
| mosip-ref-impl       | [v1.3.0-beta.2](https://github.com/mosip/mosip-ref-impl/tree/v1.3.0-beta.2)       |
| registration-client  | [v1.3.0-beta.1](https://github.com/mosip/registration-client/tree/v1.3.0-beta.1)  |
| audit-manager        | [v1.3.0-beta.1](https://github.com/mosip/audit-manager/tree/v1.3.0-beta.1)        |
| commons              | [v1.3.0-beta.2](https://github.com/mosip/commons/tree/v1.3.0-beta.2)              |
| artifactory-ref-impl | [v1.3.0-beta.2](https://github.com/mosip/artifactory-ref-impl/tree/v1.3.0-beta.2) |
| mosip-config         | [v1.3.0-beta.2](https://github.com/mosip/mosip-config/tree/v1.3.0-beta.2)         |
| demosdk              | [v1.3.0-beta.1](https://github.com/mosip/demosdk/tree/v1.3.0-beta.1)              |

**Bug Fixes**

| Jira ID                                                       | Description                                                                                                 |
| ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| [MOSIP-39903](https://mosip.atlassian.net/browse/MOSIP-39903) | Once a sub type of biometric is marked as an exception, authentication for other biometrics is not working. |

**Known Issues**

| Jira ID                                                       | Description                                                   |
| ------------------------------------------------------------- | ------------------------------------------------------------- |
| [MOSIP-40539](https://mosip.atlassian.net/browse/MOSIP-40539) | The digital card topic gets empty once the request is timed.  |
| [MOSIP-40613](https://mosip.atlassian.net/browse/MOSIP-40613) | Notifications are not being received after packet processing. |
| [MOSIP-35873](https://mosip.atlassian.net/browse/MOSIP-35873) | Operator onboarding using biometrics is failing.              |

### Documentation

* [Functional Test Report](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/1.2.1.0-beta.1-part-3/test-report)


---

# 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/1.2.1.0-beta.1-part-3.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.