Weekly notes IDBB w43
Oct 18, 2022
Attendees
@sasi
@PSRAMKUMAR
@Ramesh Narayanan
@Vishwanath V
Supporting documents
Meeting Note
Agenda | Presenter | Discussion |
|
---|---|---|---|
Live integration of IDBB into GovStack demo | Ingmar | Ingmar was not able to attend, the session will be re-arranged |
|
Contribution to Testing effort | Ramkumar | Ramkumar ask if any MOSIP resources can be dedicated to Testing effort.
|
|
Role of IDBB on Individual centric approach in GovStack | Jaume/ Ramesh | Discussion happened to consider if IDBB should have a specific role on Individual centric mechanisms. It was agreed that as Individuals are linked to their identity by the identifiers managed by directly or indirectly by IDBB, IDBB should take care to explore and propose design Individual Centric topics. Ie the link with consent, the link with digital signature, with digital safe, with claims of any kind or having a UI for indivuals. That’s why IDBB members are all also member of other WG such as Sasi who’s member of Consent and Digital Signature WG. @Jaume DUBOIS to clarify that to remaining of GovStack in a coming Tech committee. |
|
Legal Person | Ramkumar | Ramkumar reminded that IDBB should also take care to manage identification of legal entities such like companies. Jaume highlighted that in many case those legal entities are represented by individuals acting on their behalf, this bringing to management of delegation. Considering current IDBB roadmap priorities, this is in backlog but not in roadmap yet. |
|
Role Based Access Control | Jaume | The WG has discussed the different approach to manage roles:
If there are implementations of Role Based Access Management, there is no standardization of roles, and this task should not belong to transveral building block such as IDBB which should not enter in functional considerations. What can be brought is tools for transparency and accountability on those roles : being transparent on those accesses and bring trust on the way they are allocated. Sasi has mentionned all this is about resouces access management and introduced a different approach which is currently studied, which is ‘scope’ based approach instead of ‘role’ based. If this is interesting approach to follow for new system, the problem reside on how to apply to existing systems without provoking massive reworks ? Solution mentionned could be to have Gateways/Proxy managing access control on top systems to give access to Scope based on authorization of individual or of its role. |
|
Next meeting | Jaume | Welcome new comers Launch openAPI review |
|
Action Items
Decisions
- MOSIP will provide a demo instance (see 3 steps delivery plan in notes)
- [w32] IDBB will have its own UI. API and UI level switching are required but credential data security and privacy must be ensured > Meeting will happen w32 with Registration buildblock to cover that point.
- [w38] Torsten Lodderstedt (from OpenID Foundation) will join IDBB workgroup to support Authentication/KYC API definition
- [w39] GovStack demo should adapt to showcase IDBB block features capacities (added value)
- [w43] IDBB will take be involved in any Individual Centric scenario and could make some design proposals