Partner Management System Revamp 1.3.0-beta.5
Release Name: Partner Management System Revamp
Release Number: 1.3.0-beta.5
Release Date: 20th May, 2026
Overview
Partner Management System (PMS) Revamp 1.3.0-beta.5 introduces support for onboarding new partner types and includes enhancements to partner-policy validation behavior in the DataShare service. This release extends the PMS onboarding framework to support Credential Partners and Manual Adjudication Partners through complete end-to-end onboarding flows.
Key Features & Enhancements
1. Support for Credential Partner Onboarding
This release introduces support for a new partner type called Credential Partner with complete end-to-end onboarding capabilities in PMS.
Added support for:
Partner self-registration support for Credential Partners.
Policy request creation support for Partner Admins.
Root CA upload support as part of Credential Partner onboarding.
Policy request approval workflow support for Partner Admins.
Biometric Extractor configuration creation support for Partner Admins.
End-to-end onboarding lifecycle support for Credential Partners across PMS workflows.
Note : Credential Partner onboarding requires mandatory mapping of Biometric Extractors and Credential Types as part of the policy request workflow. To support this, two additional steps have been introduced in the policy request process for configuring these mappings.
The Partner Admin will not be able to approve the policy request if either of these mappings is missing or incomplete.
Please refer to the User Guide for detailed instructions and configuration steps.
Note:As part of the current release, editing an existing policy request is not supported. Once a policy request has been created and approved, the associated Biometric Extractor and Credential Type mappings cannot be modified for that policy.
If changes to these mappings are required, a new policy request must be created with the updated configuration.
Note: For a given partner, mapping the same Credential Type multiple times is not supported. Each Credential Type can be associated only once per partner.
2. Support for Manual Adjudication Partner Onboarding
This release introduces support for a new partner type called Manual Adjudication Partner with full onboarding support.
With this partner admin can:
Create new Manual Adjudication partner
Upload and re-upload partner certificates
Link relevant policies to the Manual Adjudication partner
3. Enhancement to Policy-to-Partner Validation in DataShare Service
The behavior of the following endpoint has been corrected in the DataShare service:
/v1/policymanager/policies/{policyId}/partner/{partnerId}
Enhancement Details
The endpoint validation logic has been updated to validate policy-to-partner mappings using the partner_policy_request table instead of the partner_policy table.
Deprecated APIs
/{partnerId}/credentialtype/{credentialType}/policies/{policyName}
POST
Creates mappings directly and bypasses the partner-policy request approval workflow.
/partners/{partnerId}/policies/{policyId}/credential-types-request
/{partnerId}/bioextractors/{policyId}
POST
Direct biometric extractor configuration creation/update without workflow-based approval handling.
/partners/{partnerId}/policies/{policyId}/bio-extractors-request
User Stories
Credential Partner Onboarding
Credential Partner – Login & Dashboard Display with Service Cards
Partner Admin : Display Biometric Extractor Provider Configuration Listing for Credential partner
API Service: Update endpoint PUT /partners/policy/{mappingkey} for Approve / Reject a Partner Policy Request
API Service: Add new endpoint GET /partner-policy-requests/{requestId}/credential-types-request
API Service: Add new endpoint GET /partner-policy-requests/{requestId}/bio-extractors-request
API Service: Add new endpoint POST /partners/{partnerId}/policies/{policyId}/credential-types-request
API Service: Add new endpoint POST /partners/{partnerId}/policies/{policyId}/bio-extractors-request
API Service: Correct Policy-Partner Mapping Validation in DataShare Service by Updating Endpoint Logic
API Service: Add new endpoint GET /bio-extractor-configurations/{bio-extractor-configurations-id}
API: Update GET /partner-api-keys/v2 endpoint to include partnerType in request filter and response
Manual Adjudication Partner: Remove API Key related UI Features and Manual Adjudication Services Card
Automation
PMS UI Automation: push the code from develop to release 1.3.x branch for PMS 1.3.0-beta.5 release.
Known Issues
Please refer here for the full list of known issues.
PMS Revamp-Email notifications are not received in Arabic and French languages despite user language registration
PMS Revamp- The acknowledgement Title and subtitle popping up in the UI is not as per the requirement mentioned in the story criteria
PMS Revamp- Unable to create configuration with same name and different modality – uniqueness constraint unclear in Create Biometric Extractor Provider Configuration screen
PMS Revamp- On providing invalid attribute name/extractor provider/biometric/extractorproviderversion user is still able to submit the request for bio extract request
PMS-Revamp - Policy Group Selection Fails for Authentication partner with long Organization name and username.
PMS-Revamp - Language code mismatch between Keycloak and DB During New Partner Registration for Notification Preference language.
PMS Revamp- Partner ID/Username allows more than 36 characters during registration but fails at login with validation error
PMS Revamp UI Automation: Fix all commented-out issues and remove them from UI automation.
Repositories Released
mosip-partner-management-services
mosip-partner-management-ui
Compatible Modules
Learn More
Partner Management Portal: For code and implementation of Partner Management Portal (revamp),
Test Report
For details on the test results, refer here.
Last updated
Was this helpful?