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.