MOSIP Docs 1.2.0
GitHubCommunityTech BlogsWhat's New
  • MOSIP
    • Overview
    • License
    • Principles
      • Inclusion
      • Privacy and Security
        • Security
        • Data Protection
        • Privacy
    • Technology
      • Architecture
      • Digital ID DPI Framework
      • Technology Stack
      • API
      • Sandbox Details
    • Standards & Specifications
      • MOSIP Standards
        • 169 - QR Code Specifications
        • 169 - QR Code Specifications 1.0.0
    • Inji
    • eSignet
  • ID Lifecycle Management
    • Identity Issuance
      • Pre-registration
        • Overview
          • Features
        • Develop
          • Developers Guide
          • UI Specifications
        • Test
          • Try It Out
          • End User Guide
          • Pre-registration Collab Guide
      • Registration Client
        • Overview
          • Features
        • Develop
          • Developers Guide
          • UI Specifications
        • Test
          • Try It Out
          • End User Guide
          • Registration Client Collab Guide
        • Deploy
          • Installation Guide
          • Operator Onboarding
          • Configuration Guide
          • Settings page
        • Telemetry from Registration Client
      • Android Registration Client
        • Overview
          • Features
        • Develop
          • Developer Guide
          • UI Specification
          • Technology Stack
        • Test
          • End User Guide
          • Collab Guide
        • Deploy
          • Configuration Guide
      • Registration Processor
        • Overview
          • Features
        • Develop
          • Registration Processor Developers Guide
        • Test
          • Credential Requestor Stage
          • Manual Adjudication and Verification
        • Deploy
          • Configurations Details
          • Deploy
      • ID Repository
        • Credential Request Generator Service Developers Guide
        • Identity Service Developers Guide
        • VID Service Developers Guide
        • .well-known
        • Custom Handle Implementation Guide
    • Identity Verification
      • ID Authentication Services
        • ID Authentication Demographic Data Normalization
        • ID Authentication Service Developers Guide
        • ID Authentication OTP Service Developer Guide
        • ID Authentication Internal Service Developers Guide
        • MOSIP Authentication SDK
      • ID Authentication
    • Identity Management
      • ID Schema
      • Identifiers
      • Resident Portal
        • Overview
          • Features
        • Develop
          • Developers Guide
          • UI Developers Guide
          • UI Specifications
          • Technology Stack
        • Test
          • Functional Overview
          • End User Guide
          • Collab Guide
        • Deploy
          • Deployment Guide
          • Configuration Guide
          • Configuring Resident OIDC Client
          • Browsers Supported
    • Support Systems
      • Administration
        • Develop
          • Admin Services Developers Guide
        • Test
          • Try it out
          • Admin Portal User Guide
          • Admin Portal Collab Guide
        • Masterdata Guide
      • Partner Management System
        • Partners
        • Overview
          • Features
        • Develop
          • Architecture
          • Technology Stack
          • Backend Developers Guide
          • UI Developers Guide
          • Build and Development Guide
          • New Language Support
          • Browsers Supported
        • Test
          • Try It Out
          • Partner Administrator
          • Policy Manager
          • Authentication Partner
          • Device Provider
          • FTM Chip Provider
          • PMS Collab Guide
        • Deploy
          • PMS Configuration Guide
          • API changes with PMS Revamp
        • PMS Legacy
          • Partner Management System
          • Partner Management Portal
          • Auth Partner
          • Device Provider
          • Foundational Trust Provider
          • Partner Management Services Developers Guide
      • Reporting
        • Anonymous Profiling Support
    • Supporting Components
      • Biometrics
        • ABIS
        • ABIS API
        • Biometric SDK
        • Biometric Devices
        • FTM
        • Biometric Specification
        • MDS Specification
        • CBEFF
        • Compliance Tool Kit
      • Commons
        • Commons Developers Guide
        • Audit Manager Developers Guide
        • OpenID-Bridge Developers Guide
        • ID Generator
      • Datashare
      • Keycloak
      • Persistence
        • Postgres DB
        • Object Store
      • Packet Manager
        • Registration Packet Structure
      • Quality Manager
        • Automation
          • API Test Rig Automation
          • DSL Test Rig Automation
          • UI Test Rig Automation
          • Automation Testing
        • Manual
    • Supporting Services
      • Mock Services
      • Key Manager
        • Keys
        • Hadware Security Module (HSM)
        • Key Manager Developers Guide
      • Module Configurations
      • WebSub
        • WebSub Developers Guide
  • Setup
    • Deployment
      • Getting Started
        • Helm Charts
        • Versioning
        • Wireguard
          • Wireguard Bastion Host
          • Wireguard Administrator's Guide
          • Wireguard Client Installation Guide
        • Production
          • Server Hardware Requirements
          • Production Hardening Guide
          • Administration Using Rancher
      • V3 installation
        • On-Prem Installation Guidelines
        • On-Prem without DNS Installation Guidelines
        • AWS Installation Guidelines
        • Testrig
        • MOSIP External Dependencies
        • MOSIP Modules Deployment
    • Implementations
      • Implementations
      • Reference Implementations
    • Upgrade
      • Adopting LTS 1.2.0
        • Upgrade Runbook
          • Deployment Architecture Upgrade
          • Platform Upgrade
          • Additional Information
            • Handling Duplicate Entries
            • Adapting Changes in Administration Roles
            • Identifying Applicant Type
            • Changes in Camel Route
            • Changes in Role Management based on Client IDs
            • Handling Case Insensitive Duplicated User Details
            • Managing Unequal Certificates
            • Update Identity Mapping file in Configuration
            • New Datashare Properties
            • Handling Non-Recoverable Packets
            • Partners' Certificate Expired
            • Handling Partner Organization Name Mismatch Issue
            • Pre-Registration UI Upgrade
            • Registration Client Upgrade
            • Guide to Reprocess Packets Manually
        • Documentation for 1.1.5
      • Java 21 Migration Guide
  • Interoperability
    • Integrations
      • MOSIP - CRVS
        • Scope
        • Approach
          • Technical Details
        • Existing Integrations
          • OpenCRVS
      • MOSIP e-Manas
      • Digital Signature
      • MOSIP Token Seeder
        • MTS Versions
          • Version 1.0.0
          • Version 1.0.1
          • Version 1.1.0 (WIP)
        • MTS Developer Guides
          • Developer Guide 1.0
          • Developer Guide 1.1
        • MTS Connector
        • OpenG2P-registry MTS Connector
      • MOSIP eSignet
        • ID Authentication
        • Partner Management
        • Configuring eSignet
      • Print Service Integration
        • Verified Credentials
  • Community
    • Contributions
    • Code Contributions
      • Code of Conduct
      • MOSIP Release Process
        • Go/No Go Release Checklist
      • MOSIP Branching Strategy
    • Community Calendars
    • Documentation Credits
  • Roadmap and Releases
    • Roadmap
      • Roadmap 2025
      • Roadmap 2024
      • Roadmap 2023
    • Releases
      • Partner Management System Revamp (Patch)
      • Registration v1.2.1.1
      • PMS Revamp Release 1.2.2.1 (Patch)
      • v1.2.1.0 - Registration Processor
        • Test Report
      • Android Registration Client v0.11.0
        • Test Report
      • API Test Commons Releases
        • v1.3.2
        • v1.3.1
        • v1.3.0
      • 1.2.1.0-beta.1 (Part 3)
        • Test Report
      • Partner Management System 1.2.2.0
        • Test Report
      • Resident Services v0.9.1
        • Test Report
      • 1.2.0.2 - Reg Processor & ID Repo
        • Test Report
      • 1.2.1.0-beta.1 (Part 2)
        • Enhancements and Bug Fixes
        • Test Report
      • 1.2.1.0-beta.1(Part 1)
      • Android Registration Client 0.11.0-beta.1
        • Test Report
      • Partner Management System 1.3.0-dp.1
        • Test Report
      • 1.2.2.0 (Mosip - Config)
      • Api Test Commons Releases
      • Android Registration Client v0.10.0
        • Test Report
      • Resident Services 0.9.0
        • Test Report
      • 1.2.1.0 (ID Authentication)
        • Functional Test Report
      • 1.2.0.2
        • Test Report
      • 1.2.0.1
        • Enhancements and Bug Fixes
        • Test Report
      • Android Registration Client 0.9.0
        • Test Report
      • 1.2.0.1-B4 (Beta)
        • Test Report
      • Android Registration Client DP1
      • Resident Services DP1
      • 1.2.0.1-B3 (Beta)
        • Test Report
      • 1.2.0.1-B2 (Beta)
      • 1.2.0.1-B1 (Beta)
        • Functional Test Report
        • Sonar Report
      • 1.2.0
        • Enhancements
        • Functional Test Report
        • Sonar Scan Report
        • Performance Test Report
        • Security Test Report
        • Feature Health Report
  • General
    • Glossary
    • Resources
    • MOSIP Support Policy
    • Collab Environment Guides
      • Use Cases
        • Loan Application
      • Generating Demo Credentials
    • MOSIP Documentation Style Guide
Powered by GitBook

Copyright © 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.

On this page
  • FTM Chip Provider
  • What all activities can a 'Partner Admin' perform for FTM Chip Provider?
  • CA Signed Partner Certificate Upload / Download or Re-Upload
  • Upload CA signed Certificate
  • Download Certificate
  • Download Certificate
  • Re-Upload Certificate**
  • FTM Chip Provider Services
  • Add FTM Chip:
  • Partner Admin
  • Manage Certificate for approved records
  • Deactivate FTM Chip

Was this helpful?

Edit on GitHub
Export as PDF
  1. ID Lifecycle Management
  2. Support Systems
  3. Partner Management System
  4. Test

FTM Chip Provider

Last updated 2 months ago

Was this helpful?

FTM Chip Provider

Partner Management System (PMS) is used by both; PMS Admin and Partner User.

  • Partner Administrator: Partner Admin

  • Partners: Partner User

What all activities can a 'Partner Admin' perform for FTM Chip Provider?

Being a 'Partner Admin' you can perform following activities to complete the end to end functionality pertaining to Device Provider.

  • Upload Root CA and Sub CA Certificates

  • Approve/Reject FTM Chip

Upload Root CA and Sub CA

Only after Partner Admin 'Upload Root CA and Sub CA Certificates' that a Partner will then be able to Upload CA signed Partner Certificate.

As a process of Partner onboarding onto PMS after successful registration, Partner is required to Upload CA signed Partner Certificate on behalf of their organisation which would be used to build a trust store in MOSIP to cryptographically validate that they are from a trusted organisation.

Certificate Authority (CA) is an organization that acts to validate the identities of entities (in this case, a partner organisation) and bind them to cryptographic keys through the issuance of electronic documents known as digital certificates. A country needs to onboard valid CAs before onboarding any partner as MOSIP will only accept certificates which are signed only by a Trusted CA.

Upload Root CA and Sub CA Certificates

  1. Go to PMS Portal and login as Partner Admin. Click on Certificate Trust Store in Admin dashboard

  1. Within Root CA tab - click on Upload Trust Certificate button on the top-right of the screen.

  1. Select the Partner Domain, (FTM)

  1. Choose the Root CA Certificate to upload (only files with extensions as .cer or .pem).

  1. Click Submit and an appropriate success message appears.

  2. Similarly, Sub/Intermediate CA certificate should be uploaded by following the above steps (2-4) by navigating to Upload Intermediate CA Certificate button provided within Intermediate Root CA tab.

What all activity can a Partner (FTM Chip Provider) perform?

To be able to access the services by PMS and to validate that the partner is from a trusted organisation, undergoing self registration on PMS and uploading CA signed certificate is necessary. Here is what you are able to do as FTM Chip Provider:

  • Self Register on PMS Interface

  • Upload CA signed Certificate

Self-Register on PMS as FTM Chip Provider

  1. The FTM Chip Provider can register themselves on MOSIP PMS portal by clicking Register on the Login Page, a form comes up.

  2. Enter the FTM Chip Provider details:

    1. Partner type (FTM Provider)

    2. First and Last name

    3. Organization Name

    4. Address, Phone number

    5. e-mail, Username and password

  1. On successful registration, you will be asked to read through 'Terms and Conditions' and having carefully read through it you can agree and accept it.

Validations:

  • Terms & Conditions: Partner consent refers to voluntary and informed agreement provided by a partner user on behalf of the Partner Organisation, to a specific action or process where the users have a clear understanding of what they are consenting to. User consent is important to ensure data privacy, where it is compliant to obtain explicit consent from partners before collecting, processing, or sharing their personal / organisation level data.

  • A detailed description explaining which of their personal and organisation data is used and for what purposes it will be used in PMS will be informed while seeking user consent.

Login:

  • For existing partner users who are already registered in Partner Management System, they can login to the portal with their email, username and password.

  • On logging in you come to Partner Dashboard (considering the pre-requisites such as policy group selection and consent are already completed).

Forgot Password:

  • Partner user has an option to reset password , you can use it when you forget password or want to change password after a certain duration.

CA Signed Partner Certificate Upload / Download or Re-Upload

  1. Partner Certificate

  2. FTM Chip Provider Services

These features can also be accessed by clicking on side panel (in the form of icons) or clicking on the hamburger menu on the top left which is available across all screens of PMS to help user easily navigate.

Once registered as a process of Partner onboarding onto PMS after successful registration, user is required to Upload CA signed Partner Certificate on behalf of their organisation which would be used to build a trust store in MOSIP to cryptographically validate that they are from a trusted organisation.

Tips:

Later when required a Partner can also 'Download Certificate' and 'Re-Upload Certificate' (As the need may be).

Important:

Before a Partner can upload a 'CA Signed Certificate' it is prerequisite that the 'Partner Admin' should have already had uploaded the Root CA and Intermediate CA certificates.

Upload CA signed Certificate

  1. Go to FTM Provider > Dashboard.

  1. Click on Partner Certificate option, Click on the Upload button to upload the partner certificate signed by CA.

  1. Select the CA signed partner certificate from local system by tapping on the upload section (blue area).

  1. The required certificate is selected from the local system.

  1. Certificate is successfully fetched from local system.

  1. Click on Submit, Partner Certificate is uploaded successfully.

  1. On closing the popup, The user can view the uploaded certificate details in the form of a list view.

Download Certificate

There is also an option to download initially uploaded CA signed certificate and also the MOSIP Signed Certificate.

Success Message is displayed on successful download of Originally uploaded certificate/ MOSIP Signed Certificate.

On closing the popup the user can view the uploaded certificate details in the form of a list view.

Download Certificate

There is also an option to download initially uploaded CA signed certificate and also the MOSIP Signed Certificate.

Re-Upload Certificate**

Re-uploading certificate is required in cases when MOSIP Signed Certificate gets expired after one year.

Note:

'MOSIP Signed Certificate has a validity of 1 year from the time of Partner Certificate Upload.

You must ensure that you re-upload the partner certificate again so that new MOSIP signed certificate can be generated and other functionalities such as FTM Chip Provider Services can function.

The rest of the steps is same as covered in Upload Certificate flow (Step 3-7)

FTM Chip Provider Services

After the partner has uploaded partner certificate he can now perform 'FTM Chip Provider Services':

  • Add FTM Chip details and upload the FTM Chip certificate for the request to be sent to partner admin for approval.

  • Deactivate FTM details.

  • Re-upload and Download FTM Chip Certificate.

Add FTM Chip:

You can add details of Foundational Trust Module (FTM) chip by clicking on 'Add FTM Chip' button which takes you to 'Add FTM Chip Details' screen.

The partner is expected to enter the make and model of FTM Chip and submit the details.

After successful submission of FTM Chip details, the partner is prompted to click on 'Upload FTM Chip Certificate' to proceed further.

The partner clicks on the Upload section to select the FTM Chip Certificate from local system.

After selection, the uploaded certificate is displayed on screen which the partner has to submit.

A success message on successful submission is displayed on the screen.

On click of Close you come back to List of FTM Chip details page where the status of the record is in 'Pending for Approval status'.

Let's assume, the certificate upload process was not carried out after adding FTM details due to a technical issue / unexpected closing of the PMS portal. At such instances, while navigating to FTM Chip Services Dashboard → List of FTM Chip details, the given record is found to be in 'Pending for Certificate Upload' status. Which means that without the certificate upload the record will not go to admin for approval..

To upload the FTM Chip certificate, select the Manage Certificate option from action menu.

The partner is navigated to Manage FTM Chip certificate page where on clicking upload button, the partner can upload the certificate by following the same steps as mentioned above.

Once the upload is complete - the record moves to 'Pending for Approval' status where the Partner Admin can take appropriate action by approving / rejecting this entry.

Partner Admin

To approve / reject an FTM Chip, admin clicks on 'FTM Chip' card in his homepage.

The admin navigates to 'List of FTM Chip details' page where list of all FTM Chip records submitted so far by different FTM Chip providers are displayed.

On clicking the action menu of the respective FTM Chip record, an option 'Approve/ Reject' is provided.

A popup window appears for the admin to take appropriate action- Approve / Reject and select the respective button.

The status is thus updated accordingly in List of Devices Page as Approved / Rejected based on the above action.

Note:

'Pending for Approval' status is displayed when the FTM Chip request is pending with admin for approval and no action has been taken by admin yet.

Manage Certificate for approved records

Once the FTM Chip record is approved, FTM Chip Provider can click on Manage Certificate option in action menu so that the partner can download / reupload the FTM Chip certificate in Manage FTM Chip Certificate page.

To re-upload certificate after expiry or otherwise, click on Re-Upload button.

Follow the same steps as upload flow to perform the reupload functionality.

After reupload of certificate is successfully completed, the status again changes to 'Pending for Approval' as the renewed certificate needed to go through admin check for the FTM Chip record to be validated.

Every Approved FTM Chip record has a download option provided to download the FTM Chip certificate at any given time.

on click of download button, a success message is displayed on the screen.

Deactivate FTM Chip

Partner / Partner Admin can deactivate an active FTM Chip any time provided it is in 'Approved' status. To perform deactivation, click on 'Deactivate' option in the action menu of the given FTM Chip in 'List of FTM Chip details' page.

On clicking 'Deactivate', a popup window appears seeking for confirmation and appropriate info text is displayed.

On deactivation , the status changes to 'Deactivated' status.

User is now in where the following features are provided to FTM Chip Provider:

Home Page/Dashboard