Identity qrcodes

[armanddidierjean]

Description

Summary

Allows to generate and scan qrcode attesting of a user identity

The user should first ask for a token:
POST /identity/users/me/create-token
This token will be valid for 2 minutes, the client should generate a qrcode containing this token

The person verifying the identity should first choose a context. A context correspond to a situation where qrcode will be verified, it typiccally correspond to an event for which we want to keep the list of participants.
With its context, the verifier should scan the qrcode of the user.
The verifier client should
GET /identity/verification-contexts/{context_id}/scans/{token}/info
to get information about the user, and show this information to the verifier.
already_scanned indicates if the user identity was previously scanned for the current context. It may be used to ensure people can only enter once.
The client should present a button asking if the verifier wants to scan this user (typically, if the user entry is granted, the identity will be scanned, otherwise if the user entry is refused, the verifier won't scan the identity)

To scan the identity, the client should
POST /identity/verification-contexts/{context_id}/scans/{token}/scan

Classification

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• [ x ✨ New feature (non-breaking change which adds functionality)
• 🔨 Refactor (non-breaking change that neither fixes a bug nor adds a feature)
• 🔧 Infra CI/CD (changes to configs of workflows)
• 💥 BREAKING CHANGE (fix or feature that require a new minimal version of the front-end)
• 😶‍🌫️ No impact for the end-users

Impact & Scope

• Core functionality changes
• Single module changes
• Multiple modules changes
• Database migrations required
• Other: ...

Testing

• 1. Tested this locally
• 2. Added/modified tests that pass the CI (or tested in a downstream fork)
• 3. Tested in a deployed pre-prod
• 0. Untestable (exceptionally), will be tested in prod directly

Documentation

• Updated the docs accordingly :
• " Docstrings
• # Inline comments
• No documentation needed