mirror of
https://github.com/corona-warn-app/cwa-documentation
synced 2024-11-29 12:44:27 +01:00
docs(evreg): use base64url instead of base64 in QR code
This commit is contained in:
parent
38b6127cb1
commit
1a75364c67
@ -115,18 +115,18 @@ message CWALocationData {
|
|||||||
|
|
||||||
The ID of a venue is derived as the SHA-256 hash of the concatenated byte representation of the string `CWA-GUID` and the byte representation of the Protocol Buffer message `QRCodePayload`. The `cryptographicSeed` adds sufficient entropy so that any modifications to the QR result in a unique ID.
|
The ID of a venue is derived as the SHA-256 hash of the concatenated byte representation of the string `CWA-GUID` and the byte representation of the Protocol Buffer message `QRCodePayload`. The `cryptographicSeed` adds sufficient entropy so that any modifications to the QR result in a unique ID.
|
||||||
|
|
||||||
A `QRCodePayload` is base64-encoded and included in a URL. The URL is the content of the QR code and structures as follows:
|
A `QRCodePayload` is base64url-encoded and included in a URL. The URL is the content of the QR code and has the following structure:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
https://e.coronawarn.app?v=1#<base64_encoded>
|
https://e.coronawarn.app?v=1#<base64url_encoded>
|
||||||
|
|
||||||
# example:
|
# example:
|
||||||
CWA Germany:
|
CWA Germany:
|
||||||
https://e.coronawarn.app?v=1#Y3dh...
|
https://e.coronawarn.app?v=1#Y3dh...
|
||||||
NotifyMe CH:
|
NotifyMe CH:
|
||||||
https://qr.notify-me.ch?v=2#bm90aWZ5bWU=
|
https://qr.notify-me.ch?v=2#bm90aWZ5bWU
|
||||||
CLEA FR:
|
CLEA FR:
|
||||||
https://tac.gouv.fr?v=1#Y2xlYQ==
|
https://tac.gouv.fr?v=1#Y2xlYQ
|
||||||
```
|
```
|
||||||
|
|
||||||
### QR Code Compatibility with Other Contract Tracing Apps in Germany DRAFT
|
### QR Code Compatibility with Other Contract Tracing Apps in Germany DRAFT
|
||||||
@ -142,7 +142,7 @@ Other contact tracing apps in Germany that leverage QR code for Presence Tracing
|
|||||||
| `<URL>` | The URL associated with the respective contact tracing apps, with or without a partial path. |
|
| `<URL>` | The URL associated with the respective contact tracing apps, with or without a partial path. |
|
||||||
| `<VENDOR_DATA>` | Any vendor-specific data such as the venue id in the vendor's system. This data may be passed to the vendor-specific app upon interaction by the user if a deeper integration is required. |
|
| `<VENDOR_DATA>` | Any vendor-specific data such as the venue id in the vendor's system. This data may be passed to the vendor-specific app upon interaction by the user if a deeper integration is required. |
|
||||||
| `[VENDOR_ADDITIONAL_DATA]` | Additional vendor-specific data (optional). |
|
| `[VENDOR_ADDITIONAL_DATA]` | Additional vendor-specific data (optional). |
|
||||||
| `<ENCODED_PAYLOAD>` | A representation of the Protocol Buffer message `QRCodePayload` encoded in base64. Note that the signature must have been created by the CWA Server. |
|
| `<ENCODED_PAYLOAD>` | A representation of the Protocol Buffer message `QRCodePayload` encoded in base64url. |
|
||||||
|
|
||||||
**Note:** Any contact tracing apps that integrate with CWA must ensure that they do not process any information from the CWA part of the QR code.
|
**Note:** Any contact tracing apps that integrate with CWA must ensure that they do not process any information from the CWA part of the QR code.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user