QuickWin Alignment Meeting 13th October 2023

Attendees

@Aleksander Reitsakas

@Jaume DUBOIS

@sasi

@smita.selot

Agenda

To understand the overlaps and gaps between IDBB Relying Parties management and what IM is already covering

Minutes of the meeting

1. IM provides authentication for organizations.

2. IM has the capability to register partners but does not define any policies for partner management.

3. Each partner is given a code after it registers with IM using its organization ID. Mapping of code to organization ID is done at the time of partner configuration.

4. There is a possibility of using X-Road Groups for policies. This possibility has to be explored in detail.

5. Currently, IM capabilities can only provide infrastructure-level authentication, i.e. similar to authentication for MISP in MOSIP.

6. Capabilities to share KYC details with commercial players based on policies is missing from IM.

7. It is recommended to use IM for communication between building blocks.

8. In MOSIP, each partner uses a specific MISP, and relying party policies are built on top of that. Each relying party is given a license.

9. IM-based code to MOSIP-based license for the relying party may be needed.

10. IM has APIs for getting the list of all members and applications, a description of services, services availed by each application, and allowed services.

Action items

Smita: to explore partner management and policy management in detail