Weekly notes IDBB w2 (2023)

Dec 4, 2022

Attendees

  • @sasi

  • @Ramesh Narayanan

  • @Vishwanath V

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Kick-off 2023

 Jaume

Sharing about the expectations for IDBB in 6 coming months:

  • Wrap-up the ID Mapping to enable use case with Functional system or payment

  • Specify APIs for Enrollment for on-boarding of users in GovStack

News:

  • IDBB procurement is over, starting work with Technoforte

  • Need to focus efforts on supporting G2P/P2G use cases, notably on Payment

ID Mapping

Jaume

We have clarified how the mapping should happen (on-boarding use case, linking an existing functional ID) for authentication with an external identifier and using IDBB Foundational ID IDP a mapper component should be prepared, delivered by the IDBB and instanciated by the functional systems themselves > definition to be done.

Next step to wrap-up and share with other BB.

Enrollment

Jaume

We have listed the following hot points for Enrollment

TRUST

  • How do we trust the data

  • Data need to be signed

  • We need a partner application

  • Client software is trusted

PRIVACY

  • Make sure it’s only data required are collected

  • Make sure data are not copied for some more usages

DATA FORMAT

  • How can it be dynamic ?

  • Language variation

  • Biometrics standards (ISO) JPG2000, WSQ

  • Use of OpenFormats

Additionaly:

  • MOSIP is working on standardization of Identity profiles with OIDf we should be capable to leverage that work soon

  • Verifiable Credential: GovStack needs to address the classical enrollment way (declarative + based on evidences scan) but should also consider future way (verifiable digital credentials) > to be addressed as part of the work on enrollment, work closely with @Ingmar Vali on that as it won’t apply only to IDBB but to all Applications in GovStack.

 

 

Action Items

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 (https://github.com/GovStackWorkingGroup/bb-id
[w32] @Jaume DUBOIS to invite @Ingmar Vali in next meeting in order to talk about UIs integration
[w32] @Jaume DUBOIS to go on test plan draft ( https://govstack-global.atlassian.net/l/cp/uPoPtZMy ), it will be moved into GitHub once format will be understood > will need @Taylor Downs support
[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 > URL/openAPI not yet ready, still open, should be resolved by w41
[w39] @sasi to formalize API with support from @Jaume DUBOIS will be ready on w41
[w41] @Jaume DUBOIS will prepare a web sequence diagram to illustrare a generic ID Attribute sharing based on a consent given. It will be reviewed this week within the working group and if agreed will be presented as part of the Technical Committee of w41 > Draft sequence diagram is there (under internal review)
[w42] Vishwa/Sasi to make sure the openAPI proposal is properly commented for easy understanding from reviewers
[w42] Jaume to organize a review on MCPPC use case with @Ingmar Vali @Satyajit Suri @PSRAMKUMAR IDBB WG
[w42] Jaume to invite Rachel to next IDBB meeting
@Jaume DUBOIS to notify Satya of the potential reuse of MOSIP test tool and to organize review of it with GS Test team
@Jaume DUBOIS to re-organize the live integration of IDBB in GovStack demo
@Jaume DUBOIS to inform Tech Committee and other remaining of GovStack about the Central role that plays IDBB in interactions with Individuals and the fact that IDBB may be involved and propose design/scenario around that when needed. Also indicate that IDBB members may be involved in other WG for this purpose.
@Jaume DUBOIS to check @Ingmar Vali availability to start prototyping enrollment integration in demo
@Jaume DUBOIS to trigger Verifiable Digital Credential cross building block work to enable IN/OUT use of VC > start by describing the goals

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)
  5. [w43] IDBB will take be involved in any Individual Centric scenario and could make some design proposals