PMS Revamp 1.3.0-beta.1
Release Name: Partner Management System Revamp 1.3.0-beta.1
Release Number: v1.3.0-beta.1
Release Date: Coming Soon
Overview
We are excited to announce the release of PMS Revamp v1.3.0-beta.1, featuring a Java 21 upgrade and the introduction of Certificate Expiry Notifications within Partner Management System (PMS). The feature enables proactive monitoring and timely alerts for expiring certificates- Root CA Certificate, Intermediate CA Certificate and Partner Certificate through both PMS Portal and email, helping partners and partner admins take necessary action in advance.
Key Features
I. Certificate Expiry 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:
Partner Admins
Expiry alerts for all Root / Intermediate CA certificates (irrespective of who uploaded them). Weekly summary of partner certificates expiring in the next 7 days.
Partner Users
Alerts for partner certificates uploaded by them or associated MOSIP-signed certificates.
c) Notification Schedule: For Individual Certificates (Root CA / Intermediate CA / Partner Certificate):
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 partner certificates expiring within the next 7 days
e) Language Handling:
Based on the user's registration language
PMS Portal
Based on the language selected at login, overriding registration preferences
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 Certificate Expiry Notifications
Audit logging has been implemented for all certificate expiry notifications (Root CA, Intermediate CA, Partner Certificates, 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.
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' 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.
User Stories
Intermediate CA Certificate Expiration
Notification displayed on notification panel in PMS portal
Weekly Summary of Partner Certificate
Notification displayed on notification panel in PMS portal
View list of partner IDs whose partner certificates are expiring in a given week via email
View list of partner IDs whose partner certificates are expiring in a given week on PMS portal
List of all user stories pertaining to this release are available here.
Known Issues
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.
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.
Error message is displayed when same Make and Model is entered for two different SBI versions.
Able to Approve the Expired SBI which is in pending for approval status
(IDA Issue) Authentication is still Active from IDA even after deactivating the API key from the Partner Portal in PMS
(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.
Still able to approve/reject the policy even after respective authentication partner is deactivated.
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.
Partner domain dropdown items (AUTH/ DEVICE/ FTM) are in English and do not support multi-language.
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.
Repositories Released
partner-management-services
v1.3.0-beta.1
partner-management-portal
v1.3.0-beta.1
mosip-openid-bridge
v1.3.0-beta.2
mosip-data
v1.3.0-beta.2
Compatible Modules
The following table outlines the tested and certified compatibility of PMS 1.3.0-beta.1 with other backward compatible modules.
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.
Documentation
Test Report
Last updated
Was this helpful?