Weekly notes IDBB w32

Owned by Jaume DUBOIS
Last updated: Mar 28, 2023
3 min read

Aug 2, 2022

Attendees

  • @Ramesh Narayanan

  • @sasi

  • @PSRAMKUMAR

  • @Taylor Downs

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

 IDBB demo, where to host ?

 Jaume

 Option 1] MOSIP could propose to host the instance, Ramesh to check and come back next week on what’s possible. [w31/Ramesh: possible to deliver a MOSIP instance within August (2-3 weeks from now) and with Alpha version for OIDC and Biometrics early September (+4 weeks) + 4 weeks for a final version] [Priorities: Authentication, Attributes sharing]

Option 2] Extend the existing demo environment to host required MOSIP platform, need to define requirements, could be done by the bidders on IDBB. As this is resource to be addressed in the resources review meeting (this Thursday ? TBC)

 OIDC detailed objectives, OIDC falk on-boarding

Jaume 

 Clarification and alignment where made today

  • We should have contributor people and reviewers

    • ie MOSIP is going to come with draft proposals on OIDV, VC, .. we should have reviewing meeting/audience

    • We would like to have OIDC people on-boarded as contributors and for sure in review

  • For joining WG OIDC people should follow the ‘Call for expert process’ then they will be on-boarded officialy

  • Coming new features in OIDC, openID VC supporting VC (replacing somewhere OIDC profiles), leverage similar protocols

  • MOSIP is exploring with OIDC folks the use of biometrics with OIDC, a draft proposal will be presented before mid-August (ideally in a couple of weeks)

  • VC will move us to the concept of Claims that could be generalized to Functional IDs

  • Mission of IDBB is notably to be capable to make sure data belongs to a person even if those data are external from the Foundational ID (this relay to concept of Alias and ID Mapping mechanism)

  • In the end an individual could expose a set of VC which could access to could be granted to relying parties including with preliminary individual consent

[W31]

  • Need to shortly introduce GovStack/IDBB in today’s meeting with OIf

    • GovStack intro/goals, IDBB overview (use this summary slide), explain key services

  • Need to be clear on what we expect

    • We need visibility on OIDC VC roadmap

    • We need clarity on Interoperability of profile using VC

    • We would need some identified names with roles. They could come as reviewer, could contribute to specific meeting

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 go on test plan draft ( Test plan [DRAFT] - GovStack - GovStack Wiki ), 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 auditable logs - transaction log, administrative changes log, performance log, security log

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 with Registration buildblock to cover that point.