Weekly notes IDBB w39

Sep 20, 2022

Attendees

  • @Ramesh Narayanan

  • @sasi

  • @PSRAMKUMAR

  • @Torsten Lodderstedt (Unlicensed) (OpenID Foundation)

  • @Eskandar, Hani

  • @Ingmar Vali

  • @Satyajit Suri

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

 Presentation of MOSIP IDBB demo

 Sasi

Show case value of current demo version features

 Present GovStack demo, figure out how to the best showcase value from IDBB

Ingmar

1/ Autoform filling of mother details from IDBB after mother authentication, consent given per attributes

2/ Process operator authentication using IDBB authentication instead of KeyCloack

 

Way forward

Hani

1/ Integrate the current IDBB demo within the GovStack taking opportunity sure to leverage current value delivered by this 1st IDBB demo

  • Use #1 : Use it for auto-form-filling of ID attributes of Mother by redirecting to a mother authentication window which allows to consent on attributes sharing then send back to Application screen

  • Use #2 suggested by Ingmar : Use it for operator authentication option, the Health worker could choose its Foundational ID to authenticate to the Application system.

Actions:

              [_] Sasi will send the URL and the API to be used for sending request/receiving answer

              [_] Jaume will organize a second call to continue working on the technical integration of MOSIP Demo/GovStack demo

              [_] Sasi with Jaume’s support to draft current APIs in GitHub

 

2/ Enable capacity to use a previously given consent to avoid the authentication step in the individual’s attributes sharing

This way we will ensure we apply ‘privacy by design’ in IDBB.

This requires integration with consent for storage and collection of a consent > discussion already held with Ain from Consent WG, they’re not yet ready for it > We will do that on a further step

 

3/ Develop the attribute sharing service in IDBB based on a previously given consent (no authentication required) and integrate it in demo

              This will require consent to be capable to store and retrieve a given consent

This will require to implement the corresponding API in IDBB (‘GetIdentityProfile’ already identified in roadmap)

  • This will enable auto-form-filling of Baby identity information without its authentication, but with the Mother previously collected consent

 

Here is link to Miro drafted by Sasi with some of more arrangements > I’ll consolidate formalization functional design leveraging that diagram, update of diagrams reviewed with Consent WG and output of next call with Ingmar.

              [_] Jaume to organize meeting with Ingmar/Sasi (1:30 hour) for continuing the technical integration (coming Friday ?)

 

Action Items

@Jaume DUBOIS to book a regular IDBB review on Thursday’s 10:30 CET to review action status/tackle issues
Invite @Taylor Downs for the next week to talk on APIs roadmap for the short term also about what application level responsibilities (ie errors management, redirecting)
@PSRAMKUMAR should talk to @Esther Ogunjimi (Unlicensed) about the best way to report weeklies on Confluence (my recommendation is to have cumulative way, which allows to have access to whole history, to have a precise follow-up and to write little notes each time) on-hold
@Taylor Downs give access to IDBB GitHub to Jaume, Ramesh and Sasi (GitHub - GovStackWorkingGroup/bb-identity: The ID Building Block for GovStack
[w32] @Jaume DUBOIS to invite @Ingmar Vali in next meeting in order to talk about UIs integration
[w32] @Jaume DUBOIS to define how/who will manage spec migration into GitHub format (for now on-hold until clear guideline received)
[w32] @Jaume DUBOIS Add into IDBB backlog auditable logs - transaction log, administrative changes log, performance log, security log
[w33] @Jaume DUBOIS to share a web sequence diagram to describe in details interactions for authentication and a form filling > LINK
[w39] @Jaume DUBOIS to organize a call with @sasi@Ingmar Vali to go on technical integration
[w39] @sasi to formalize API with support from @Jaume DUBOIS

Decisions

  1. MOSIP will provide a demo instance (see 3 steps delivery plan in notes)
  2. [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.
  3. [w38] Torsten Lodderstedt (from OpenID Foundation) will join IDBB workgroup to support Authentication/KYC API definition
  4. [w39] GovStack demo should adapt to showcase IDBB block features capacities (added value)