Status on integration ID/Registration for Auth (wave 2)

 Ingmar

GitBook have been updated to IDBB specification v2

Integration of Authentication have been successfully performed end to end (congratulations to Vishwa and Ingmar).

Wave 3 : ID Management/on-boarding

Jaume

From next week we will start working on Wave 3.

Objective it to cover (part of) ID Management, more precisely the GovStack user on-boarding (also called Identity Enrollment in Identity domain)

As for the previous waves, we will use a prototyping approach in order to make sure we deliver proper UX and leverage what’s existing already, from statisfying running prototypes we will derive APIS and specifications.

The cases to be considered will be the following:

• First time live enrollment

  • Offline first approach

    • From Windows Laptop based kit

    • From Android tablet based kit

  • Connected approach

    • Web form based

    • Mobile App

  • We should derive an offline API from current form of connected ones

  • Being offline first allows to manage an synchronous consumption of packets by IDBB which is allowing to manage a natural flow control

  • On the other hand, it can be planned to keep an online API and to count that the Registration brick will be a client/server component which can manage itself offline mechanism.

• Importation of existing Identity

  • Leveraging existing trusted forms of Identity or trusted existing sources to fast-track population on-boarding (ie civil registration databace, ID card or passport database, Elections system, MNO, Banks, ..)

  • Question: shall we manage security of biometric data using same model as live capture. Actually, may rather go for different model of signed data verifiable vs their provider (ie using VC)

  • Other question: shall we consider batch operations or keep one by one model (knowing that creating an identity is a foundational operation, shall we take risk to generate millions of fake IDs or keep on by one management and control)

• Update of identity attributes

  • The same process and APIs would be usable to run updates on identity matching the already described multi-step enrollment process. In that case we should consider how we autorize the update as there will be some verification like authentication first and some workflow with justice

More things that are pressing to happen:

• Functional Identity, how we create more links with existing forms.

• We should equip ourselves with MOCK Functional ID to implement things around that

• Work on UI for IDBB > ID management, Preference Management, Access to audit logs, Asking for credentials, ..

• Develop Publish & Subscribe mechanisms

We need to see if we can have a quicker pace on all that, unless we will have to wait for one more year, whereas all that is somewhere already available..

Wave 3 meeting

Jaume

We will keep Tuesday’s meeting for progressing on Specs/APIs

We may have task-forces on Thursday meeting.

Friday’s meeting with Ingmar will be key to drive use by prototyping and getting feedbacks.

IDBB WG

Jaume

Our WG could be reinforced with a person which will make sure we document what we do and maintain our repositories, he/she will also be the technical interface of IDBB towards Integration and Test team.

The workgroup will keep on with the same core members which demonstrated high quality of outcome in wave 2. ID Management including enrollment should bring more players from enrollment and Credential field, also hopefully some functional ID players.