Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Attendees

Meeting Note

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

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)

  • No labels