Professional Venue Owners can register their venue with the luca system via a web application. The venue can then be managed via a web interface in order to set up individual Scanner Frontends and to configure other venue-specific parameters (for example auto checkout behavior).
The following secrets are involved in this process:
Use / Purpose
To initiate the process the Venue Owner registers with their email address and a password. They enter further information, such as the name of the venue and their contact information in the Venue Owner Frontend (see Venue Information for the complete list of the data collected).
Subsequently, the Venue Owner Frontend generates the venue keypair. Both the public and private key are stored locally. The keypair’s public key is used to set up new Scanner Frontends, which utilize it to encrypt Guests’ contact data reference during Check-In via Mobile Phone App. The keypair’s private key is needed by the Venue Owner Frontend in order to lift this encryption when assisting a Health Department in the process of Tracing the Check-In History of an Infected Guest.
Authenticity of the Venue Keypair’s Public Key¶
As the Venue Owner holds no certificate with which they could sign the public key of the venue keypair there is no secure way to validate its authenticity when it is used in the check-in process. This affects both the Check-In via Mobile Phone App and the Check-In via a Printed QR Code.
Prospectively, this will be implemented by attaching the venue keypair’s public key to the fragment component of the link to the Scanner Frontend, which is created in the Venue Owner Frontend. For printed QR codes for self Check-In the public key will be part of the QR code.