Commit 494ee6d8 authored by Jakob Heher's avatar Jakob Heher
Browse files

no longer looking for AT2 receipts!

parent 3acfd78e
......@@ -8,12 +8,12 @@ QR code data can be passed in one of three ways:
* Read from a file: `./rksv.py --file <filename>`
* Read from CLI: `./rksv.py --data <encoded data>`
For AT1 certificates, the certificate is retrieved via LDAP and signature validation is also performed.
I am looking for real-world AT2/AT3 receipts to verify a respective implementation with. If you have such a receipt, please get in touch!
For AT1 and AT2 certificates, the certificate is retrieved via LDAP and signature validation is also performed.
I am looking for real-world AT3 receipts to verify a respective implementation with. If you have such a receipt, please get in touch!
## UID resolution
Certificates are typically issued to a specified UID, not a company name. If you would like to automatically resolve this UID to a name, the parser can do this, using [the Open Data API](https://opendata.host/de/open-data).
AT1 certificates are typically issued to a specified UID, not a company name. If you would like to automatically resolve this UID to a name, the parser can do this, using [the Open Data API](https://opendata.host/de/open-data).
To do this, it requires your personal API key to be available in the `OPENDATA_API_KEY` environment variable.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment