> 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/mosip-docs-1.1.5/mosip-releases/release-notes-1.1.5.md).
# Release Notes 1.1.5
### Table Of Contents
* [Scope](#scope)
* [Documentation](#documentation)
* [Code](#code)
* [Tests](#tests)
* [a. In scope](#a-in-scope)
* [b. Not in scope or in progress](#b-not-in-scope-or-in-progress)
* [c. Test Execution Metrics](#c-test-execution-metrics)
* [Known Issues](#known-issues)
* [Critical Issues](#critical-issues)
* [Acronyms](#acronyms)
### Scope
MOSIP **1.1.5** succeeds **1.1.4** with enhancements and important defect fixes which were identified in [Release 1.1.4](/1.2.0/mosip-docs-1.1.5/mosip-releases/release-notes-1.1.4.md#list-of-known-issues).
We have also released some patch versions on top of 1.1.5, kindly view our patch documentation for the same.
**Release Date:** April 23, 2021
**Key Highlights**
* [Enhancements](/1.2.0/mosip-docs-1.1.5/mosip-releases/release-notes-1.1.5/release-notes-1.1.5-enhancements.md)
* [Defect fixes](/1.2.0/mosip-docs-1.1.5/mosip-releases/release-notes-1.1.5/release-notes-1.1.5-defect-fixes.md)
* [Patch versions](/1.2.0/mosip-docs-1.1.5/mosip-releases/release-notes-1.1.5/release-notes-1.1.5-patches.md)
### Documentation
#### 1. Platform
Includes functional requirements, process flows, architecture and high level design.
[Link to documentation](https://docs.mosip.io/platform/modules).
#### 2. APIs
All APIs are documented [here](https://docs.mosip.io/platform/apis).
#### 3. Design
Low level design documents for each module are available in the respective github repos.
### Code
* [Commons](https://github.com/mosip/commons/tree/v1.1.5)
* [Pre-registration](https://github.com/mosip/pre-registration/tree/v1.1.5)
* [Registration Client](https://github.com/mosip/registration-client/tree/1.1.5)
* [Registration Processor](https://github.com/mosip/registration/tree/v1.1.5)
* [ID Repository](https://github.com/mosip/id-repository/tree/v1.1.5)
* [ID Authentication](https://github.com/mosip/id-authentication/tree/v1.1.5)
* [Partner Management Services](https://github.com/mosip/partner-management-services/tree/v1.1.5)
* [Resident Services](https://github.com/mosip/resident-services/tree/v1.1.5)
* [Admin Services](https://github.com/mosip/admin-services/tree/v1.1.5)
* [Print Services](https://github.com/mosip/print/tree/v1.1.5)
* [Config Respository](https://github.com/mosip/mosip-config/tree/v1.1.5)
* [Durian](https://github.com/mosip/durian/tree/v1.1.5)
* [Reference Implementation](https://github.com/mosip/mosip-ref-impl/tree/v1.1.5)
{% hint style="info" %}
Code needs to be deployed as per the procedure depicted in [Sandbox Installer](https://github.com/mosip/mosip-infra/tree/v1.1.5/deployment/sandbox-v2).
{% endhint %}
### Tests
#### a. In scope
Sanity of all modules, integration testing covering all modules, new stories , bug regression, upgrade from 1.1.4 to 1.1.5
| Title | Description |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Functional Testing | - Pre-registration 1.1. (Dynamic UI & APIs)
- Registration Client (Dynamic UI, functionality)
- Kernel (APIs)
- Registration Processor
- ID Authentication (APIs)
- Partner Management (APIs)
- ID Repository (APIs)
- Resident Services (APIs)
- Admin (UI & APIs)
|
| Configuration Testing | Testing was done in 2 language schema. |
| Version Tested | v1.1.5 |
| Types of testing | - Smoke
- Functional
- Integration
- Regression
- Security
|
| Browser | Pre-Registration and Admin UI (Tested with the latest version of Chrome browser) |
| OS Support | Registration Client on Windows 10, MOSIP server components run as micro-services encapsulated as docker images |
| Areas | Technology Used |
| -------------------------------- | --------------------------------------------- |
| Deployment Script Environment | CentOS on AWS |
| Registration Client with TPM 2.0 | Windows 10 |
| Biometrics Standard | CBEFF format (Version - 2.0) |
| MDS | MDS v0.9.5 |
| ABIS | ABIS Spec Version v0.9 |
| SDK | SDK Spec Version v0.9 |
| Key-store | HSM |
| Anti-virus | ClamAV |
| Maps | OpenstreetMap |
| Transliteration | ICU4J (Library with French, Arabic languages) |
#### b. Not in scope
| Title | Description |
| ---------------------- | ---------------------------------------------------------------------------------------- |
| Fucntional Testing | - Real Biometric Testing
- All possible notifications to be tested
|
| Non-Functional Testing | - Performance Testing
- Reliability and Disaster recovery Testing
|
| HSM | Testing was done using SoftHSM |
| Browser Support | Testing for Pre-registration and Admin UI was done using Chrome (latest version) |
#### c. Test Execution Metrics
| Test Execution | Test Cases | Executed Tests | Pass | Fail | Pass% | Fail% |
| ------------------ | :--------: | :------------: | :--: | :--: | :---: | :---: |
| Pre-registration | 177 | 175 | 168 | 7 | 96% | 4% |
| Resident Services | 177 | 177 | 167 | 10 | 94% | 6% |
| Admin Services | 1040 | 1040 | 861 | 179 | 83% | 17% |
| Authentication | 122 | 138 | 95 | 43 | 69% | 31% |
| Partner Management | 42 | 42 | 40 | 2 | 95% | 5% |
| Registration | 91 | 87 | 77 | 10 | 88% | 12% |
| ID Repo | 97 | 97 | 97 | 0 | 100% | 100% |
| **Total** | 1762 | 1756 | 1505 | 251 | 86% | 14% |
### Known Issues
The top issues identified in MOSIP 1.1.5 are listed below.
| Summary | Module | Work Around |
| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Certificates are not getting populated in respective tables via websub causing trust validation or digital signature validation failures | Commons | [Support doc link](https://mosip.atlassian.net/l/c/F1Nisied) |
| Post biometric exception operator is not able to proceed ahead | Registration Client | Fix available in [registration-client:1.1.5.5-rc1](https://github.com/mosip/registration-client/tree/v1.1.5.5-rc1) |
| Registration Client syncs only ten dynamic fields | Registration Client | [Support doc link](https://mosip.atlassian.net/l/c/SnvBtN1u) |
| Pre-registration UI works for only ten dynamic fields | Pre-registration | Fix is available in [pre-registration-ui:1.1.5.3](https://github.com/mosip/mosip-ref-impl/tree/1.1.5.3/pre-registration-ui) |
| Pre-registration UI works properly only when we have full name as an attribute in id-schema | Pre-registration | Fix is available in [pre-registration-ui:1.1.5.3](https://github.com/mosip/mosip-ref-impl/tree/1.1.5.3/pre-registration-ui) |
| Remapping of machines and users is not working as expected in Registration Client | Registration Client | NA |
### Upgrade Testing
Upgrade was done from 1.1.4 to 1.1.5 , below critical issues were identified and are still open.
| Bug ID | Summary | Module |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ---------------- |
| [MOSIP-13334](https://mosip.atlassian.net/browse/MOSIP-13334) | In Reg-Client "Registration Tasks" is getting unresponsive post reg-client upgrade | Registration |
| [MOSIP-13337](https://mosip.atlassian.net/browse/MOSIP-13337) | RegClient: Unable to load Registration preview screen in all registration flow. | Registration |
| [MOSIP-13311](https://mosip.atlassian.net/browse/MOSIP-13311) | PreReg: Booked applications are not added into dashboard. | Pre-Registration |
| [MOSIP-31385](https://mosip.atlassian.net/browse/MOSIP-31385) | Reg client: Failed to fetch PRID in Registration client | Registration |
| [MOSIP-31383](https://mosip.atlassian.net/browse/MOSIP-31383) | PreReg: Post upgrade Pre-Reg applications are removed | Pre-Registration |
{% hint style="info" %}
To see all open defects, see
{% endhint %}
### Acronyms
| Acronyms | Full Form |
| -------- | --------------------------------------------- |
| MOSIP | Modular Open Source Identity Platform |
| ABIS | Automated Biometric Identification System |
| API | Application Programming Interface |
| ID | Identity |
| IDA | Identity Authentication |
| NFR | Non-Functional Requirements |
| OTP | One Time Password |
| SDK | Software Development Kit |
| JWT | Java Web Token |
| K8 | Kubernetes |
| UIN | Unique Identification Number |
| VID | Virtual ID |
| CBEFF | Common Biometric Exchange Formats Framework |
| CORS | Cross Origin Resource Sharing |
| HSM | Hardware Security Module |
| TPM | Trusted Platform Module |
| SDK | Software Development Kit |
| MDS | MOSIP Device Service |
| ICU4J | International Components for Unicode for Java |
| WIP | Work In Progress |
| TBD | To Be Determined/Done |
| MDS | MOSIP Device Specification |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.mosip.io/1.2.0/mosip-docs-1.1.5/mosip-releases/release-notes-1.1.5.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.