> 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/partner-management-system-revamp-1.3.0-beta.2.md).

# Partner Management System Revamp 1.3.0-beta.2

**Release Name**: Partner Management System Revamp 1.3.0-beta.2

**Release Number**: v1.3.0-beta.2

**Release Date**: 29th August, 2025

## Overview

We are excited to announce the release of **PMS Revamp v1.3.0-beta.2**, featuring a **Java 21 upgrade** and the implementation of **FTM Chip Certificate, SBI and API Key Notifications** in the Partner Management System (PMS) which enables proactive monitoring and timely alerts for expiring partner specific items- FTM Chip Certificates, SBI and API Keys through both PMS Portal and email, helping partners and partner admins take necessary action in advance. Additionally, we have enforced audit logs for these notifications.

## Key Features

### I. **FTM Chip Certificate, SBI and API Key Notifications**

**a) Notification Channels:**

* **PMS Portal:** In-application alerts via the notification bell icon.
* **Email:** Sent to the registered email address of the user.

**b) Recipients and Scope:**

<table><thead><tr><th width="263.8046875">Role</th><th>Notification Type</th></tr></thead><tbody><tr><td>FTM Chip Provider</td><td>Alerts for FTM Chip certificates uploaded by them.</td></tr><tr><td>Device Provider</td><td>Alerts for SBIs added by them.</td></tr><tr><td>Authentication Partner</td><td>Alerts for API Keys generated by them.</td></tr><tr><td>Partner Admin</td><td>Weekly summary of FTM Chip certificates, SBIs and API Keys created by various partners that are expiring in the next 7 days.</td></tr></tbody></table>

**c) Notification Schedule:** **For individual partner specific items (FTM Chip Certificate/ SBI/ API Key):**

* 30 days before expiry
* 15 days before expiry
* Daily reminders from 10 days prior until expiry date

**d) Weekly Summary Notifications (Partner Admins only):**

* Sent every 7 days
* Lists all FTM Chip certificates, SBIs and API Keys expiring within the next 7 days

**e) Language Handling:**

<table><thead><tr><th width="263.8046875">Channel</th><th>Language Used</th></tr></thead><tbody><tr><td>Email</td><td>Based on the user's registration language</td></tr><tr><td>PMS Portal</td><td>Based on the language selected at login, overriding registration preferences</td></tr></tbody></table>

**f) Notification Retention Policy:**

* Notifications are retained for 60 days on the PMS portal.
* Notifications older than 60 days are automatically deleted.

### II. Audit Logs for FTM Chip certificates, SBIs and API Keys Expiry Notifications

Audit logging has been implemented for all partner specific expiry notifications (FTM Chip certificates, SBIs and API Keys and Weekly Summary) sent via PMS portal and email. Success and failure events are now recorded with unique event IDs in the audit.app\_audit\_log table, enhancing traceability and monitoring.

### III. Additional Enhancements

* Auto deactivation of API Key after its expiry
* Auto deactivation of SBI after its expiry
* API Key expiration duration is configurable- Newly generated API Keys are automatically set to 100 years of expiration duration by default but the duration can also be configured via config file.
* Create utility to encrypt existing data in database
* Approve/ reject option is provided in individual pages wherever approval of partner admin is required in addition to already existing option provided in tabular views.
* Only reject option is provided to partner admins for devices that are orphaned without an SBI

### Browser Support

* Complete support on Chrome, Firefox, Edge and Safari ensures a seamless user experience across all these popular browsers.

### Language Support

* The system offers multilingual support, with resource bundles available in three languages: English, Arabic, and French. Additional languages can be easily integrated by following the guidelines provided in the ['New Language Support'](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/develop/new-language-support) documentation.

### Compatibility

* Responsive UI design for laptop/desktop views, optimized for standard browser sizes (laptop/desktop/tablet/larger screens).

For a comprehensive and detailed description of all the features, refer to [Feature Documentation](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/overview/features).

## User Stories

<table><thead><tr><th width="222.37713623046875">Feature</th><th>Sub-Feature</th><th>Jira ID</th></tr></thead><tbody><tr><td>FTM Chip Certificate Expiration (Partner Type: FTM Chip Provider)</td><td>Notification displayed on notification panel in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-39429">MOSIP-39429</a></td></tr><tr><td></td><td>Notification displayed in View all notification page in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40099">MOSIP-40099</a></td></tr><tr><td></td><td>Count of FTM Chip Certificate expiring is displayed as a dashboard badge</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40109">MOSIP-40109</a></td></tr><tr><td></td><td>Email notification</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-39439">MOSIP-39439</a></td></tr><tr><td>SBI Expiration(Partner Type: Device Provider)</td><td>Notification displayed on notification panel in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-39449">MOSIP-39449</a></td></tr><tr><td></td><td>Notification displayed in View all notification page in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40120">MOSIP-40120</a></td></tr><tr><td></td><td>Count of SBI expiring is displayed as a dashboard badge</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40130">MOSIP-40130</a></td></tr><tr><td></td><td>Email notification</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-39460">MOSIP-39460</a></td></tr><tr><td>API Key Expiration(Partner Type: Authentication Partner)</td><td>Notification displayed on notification panel in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-39470">MOSIP-39470</a></td></tr><tr><td></td><td>Notification displayed in View all notification page in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40140">MOSIP-40140</a></td></tr><tr><td></td><td>Count of API Key expiring is displayed as a dashboard badge</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40150">MOSIP-40150</a></td></tr><tr><td></td><td>Email notification</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-39480">MOSIP-39480</a></td></tr><tr><td>Weekly Summary of FTM Chip Certificate, SBI and API Key</td><td>Notification displayed on notification panel in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40220">MOSIP-40220</a><a href="https://mosip.atlassian.net/browse/MOSIP-40190">MOSIP-40190</a><a href="https://mosip.atlassian.net/browse/MOSIP-40160">MOSIP-40160</a></td></tr><tr><td></td><td>Notification displayed in View all notification page in PMS portal</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40230">MOSIP-40230</a><a href="https://mosip.atlassian.net/browse/MOSIP-40200">MOSIP-40200</a><a href="https://mosip.atlassian.net/browse/MOSIP-40170">MOSIP-40170</a></td></tr><tr><td></td><td>Email notification</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40240">MOSIP-40240</a><a href="https://mosip.atlassian.net/browse/MOSIP-40210">MOSIP-40210</a><a href="https://mosip.atlassian.net/browse/MOSIP-40180">MOSIP-40180</a></td></tr><tr><td></td><td></td><td></td></tr><tr><td>Audit Logs for FTM Chip Certificate, SBI and API Key notifications</td><td></td><td><a href="https://mosip.atlassian.net/browse/MOSIP-41811">MOSIP-41811</a></td></tr><tr><td>Auto Deactivation of API Key after its expiry</td><td></td><td><a href="https://mosip.atlassian.net/browse/MOSIP-41506">MOSIP-41506</a></td></tr><tr><td>Auto Deactivation of SBI after its expiry</td><td></td><td><a href="https://mosip.atlassian.net/browse/MOSIP-41494">MOSIP-41494</a></td></tr><tr><td>SBI - Device (Partner Admin)</td><td>Only reject option is provided to partner admins for those device records which are orphaned without an SBI</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-38189">MOSIP-38189</a></td></tr><tr><td>Approve/ Reject option provided to Partner Admin in individual view pages</td><td>Approve/ Reject option is provided for Partner Admin in all individual view pages wherever admin approval/ rejection is applicable</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-38408">MOSIP-38408</a></td></tr><tr><td>Display API Key expiration date in PMS UI</td><td>Display API Key expiration date in individual view and tabular view of API Keys details within 'Authentication Services'</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-40334">MOSIP-40334</a></td></tr><tr><td>API Key expiration duration is configurable</td><td></td><td><a href="https://mosip.atlassian.net/browse/MOSIP-41485">MOSIP-41485</a></td></tr><tr><td>Create utility to encrypt existing PII data in database</td><td></td><td><a href="https://mosip.atlassian.net/browse/MOSIP-41491">MOSIP-41491</a></td></tr></tbody></table>

List of all user stories pertaining to this release are available [here](https://mosip.atlassian.net/issues/?filter=11933\&jql=project%20%3D%20MOSIP%20AND%20%22Epic%20Link%22%20%3D%20MOSIP-32075%20and%20status%20not%20in%20%28Canceled%29%20and%20type%3D%20story%20and%20%22Release%20Number%5BLabels%5D%22%20in%20%28PMS_Release_1.3.0-beta.2%29%20ORDER%20BY%20status%20ASC).

## **Known Issues**

<table><thead><tr><th width="176.47869873046875">JIRA ID</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-34109">MOSIP-34109</a></td><td>Length validation of OIDC Client name is not functioning as expected for lengthy names within the given range. This has a dependency with eSignet, where the column size needs to be increased.Its suggested that meaningful and reasonable length be utilised for OIDC Client name.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-42553">MOSIP-42553</a></td><td>An incorrect error message is displayed when the OIDC client name exceeds the maximum allowed limit of 36 characters.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-39623">MOSIP-39623</a></td><td>Unable to select policy group in tablet and mac devices.This issue is found when more than 3000 Policy Groups are getting loaded into the Dropdown for selection. As a workaround, suggested to keep the create policy groups less than 3000.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-35343">MOSIP-35343</a></td><td>Error message is displayed when same Make and Model is entered for two different SBI versions.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-38958">MOSIP-38958</a></td><td>Able to Approve the Expired SBI which is in pending for approval status</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-39893">MOSIP-39893</a></td><td>(IDA Issue) Authentication is still Active from IDA even after deactivating the API key from the Partner Portal in PMS</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-38864">MOSIP-38864</a></td><td>(Platform Issue) Even after being deactivated by the Partner Admin, the Partner can still access and use previously created OIDC client, API key and trust Validation continues to work for the given partner.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-38383">MOSIP-38383</a></td><td>Still able to approve/reject the policy even after respective authentication partner is deactivated.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-34427">MOSIP-34427</a></td><td>On deactivating an API key from one browser , the status still remains 'Activated' on viewing the same API Key details in another browser.This is occurring due to caching. Hence user is expected to reload the tabular page of API Keys to see the latest status in View API Key screen.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-38890">MOSIP-38890</a></td><td>Partner domain dropdown items (AUTH/ DEVICE/ FTM) are in English and do not support multi-language.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-41261">MOSIP-41261</a></td><td>The partner is still able to access the PMS portal even after the MOSIP-signed certificate has expired. Also Partner is able to create Policies, OIDC Client and API Key.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43851">MOSIP-43851</a></td><td>Face attribute not present in develop and release-1.3.x(1.3 beta) branches</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43920">MOSIP-43920</a></td><td>Exclude Default Partner–Created API Keys SBI, MISP License Keys from Auto Deactivation</td></tr></tbody></table>

For more details on all the the open issues, please refer [here](https://mosip.atlassian.net/issues/?jql=parent%20%3D%20MOSIP-32075%0AAND%20status%20NOT%20IN%20%28Canceled%2C%20Closed%2C%20Fixed%2C%20Testing%29%0AAND%20%22severity%5Bdropdown%5D%22%20IN%20%28Minor%2C%20Major%2C%20Critical%2C%20Blocker%29%0AAND%20type%20%3D%20Bug%0AORDER%20BY%20issuetype%20DESC%2C%20assignee%20DESC%2C%20cf%5B10039%5D%20ASC%2C%20status%20ASC%2C%20rank).

## **Repositories Released**

| Repository Released         | Version                                                                                  |
| --------------------------- | ---------------------------------------------------------------------------------------- |
| partner-management-services | [v1.3.0-beta.2](https://github.com/mosip/partner-management-services/tree/v1.3.0-beta.2) |
| partner-management-portal   | [v1.3.0-beta.2](https://github.com/mosip/partner-management-portal/tree/v1.3.0-beta.2)   |
| mosip-data                  | [v1.3.0-beta.2](https://github.com/mosip/mosip-data/tree/v1.3.0-beta.3)                  |

## Compatible Modules

The following table outlines the tested and certified compatibility of PMS 1.3.0-beta.2 with other backward compatible modules.

{% hint style="warning" %}
**Note**: We require KeyManager v1.3.0-beta.3 to ensure that notifications are generated for Root and Intermediate Certificate expiries, as the updated version includes the new endpoint used for this functionality. However, if deployed with an earlier KeyManager version, all other features will continue to work—except the Root and Intermediate Certificate expiry notifications.
{% endhint %}

| Module/ Repo            | Version                                                                                  |
| ----------------------- | ---------------------------------------------------------------------------------------- |
| **Key Manager**         | [v1.3.0-beta.3](https://github.com/mosip/keymanager/tree/v1.3.0-beta.3)                  |
| **artifactory**         | [v1.2.0.2](https://github.com/mosip/artifactory-ref-impl/tree/v1.2.0.2)                  |
| **mosip-openid-bridge** | [v1.3.0-beta.2](https://github.com/mosip/mosip-openid-bridge/releases/tag/v1.3.0-beta.2) |
| **IDA**                 | [v1.2.1.0](https://github.com/mosip/id-authentication/tree/v1.2.1.0)                     |
| **eSignet**             | [v1.4.1](https://github.com/mosip/esignet/tree/v1.4.1)                                   |
| **Reg Proc**            | [v1.2.0.2](https://github.com/mosip/registration/tree/v1.2.0.2)                          |
| **Notifier (Kernel)**   | [v1.2.0.1](https://github.com/mosip/commons/tree/v1.2.0.1/kernel)                        |
| **Audit manager**       | [v1.2.0.1](https://github.com/mosip/audit-manager/tree/v1.2.0.1)                         |
| **ID Repo**             | [v1.2.2.0](https://github.com/mosip/id-repository/tree/v1.2.2.0)                         |
| **datashare**           | [v1.2.0.1](https://github.com/mosip/durian/tree/v1.2.0.1)                                |
| **Keycloak**            | [v1.2.0.1](https://github.com/mosip/keycloak/tree/v1.2.0.1)                              |
| **config-server**       | [v1.1.2](https://github.com/mosip/mosip-config/tree/v1.1.2)                              |
| **Websub**              | [v1.2.0.1](https://github.com/mosip/websub/tree/v1.2.0.1)                                |

## Documentation

* [Feature Documentation](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/overview/features)
* [End User Guide on Notifications feature](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/functional-overview/pms-notification)
* [Technical Guide](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/develop)
* [UI Developer’s Guide](https://docs.mosip.io/1.2.0/modules/partner-management-services/pms-revamp/technical-overview/ui-developers-guide)
* [Backend Developer’s Guide](https://docs.mosip.io/1.2.0/modules/partner-management-services/pms-revamp/technical-overview/backend-developers-guide)
* [API Documentation](https://mosip.stoplight.io/docs/partner-management-portal-revamp)
* [Test Report](/1.2.0/roadmap-and-releases/releases/partner-management-system-revamp-1.3.0-beta.2/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 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/roadmap-and-releases/releases/partner-management-system-revamp-1.3.0-beta.2.md?ask=<question>&goal=<endgoal>
```

`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.