Admin sign-in required
The access-certificate CA is admin-only.
Access-certificate CA
CA settings: name of the operator
The legal entity that runs this CA. It goes into the CA certificate when the CA is created (with the first certificate) and cannot change afterwards.
Any identifier of the operator, e.g. a VAT number or a company registration number (optional). The form VATMT-12345678 (VAT + country + “-” + number) is what wallets and relying parties expect most often.
Replace the CA (superuser)
Creates a new CA with a new name and a new key, for example to correct the organisation identifier. The old CA first signs a final revocation list for every certificate it issued; then its files are archived on the server and its key is destroyed, so it can never sign again. This site’s own verifier certificate, registration-certificate signer and (if it is ours) issuer access certificate are issued again under the new CA. Certificates of other relying parties are not re-issued: they need new ones. Wallets that pinned the old CA must pin the new one.
The relying-party register is kept. Check that your own register entry carries the same organisation identifier: the certificates issued to this site take it from there.
The CA
Register a relying party
Any identifier from an official record, e.g. a VAT number, a company registration number or an LEI. The form type + country + “-” + number (VATMT-12345678, NTRMT-C12345, LEIXG-…) is what wallets expect most often.
Contact – at least one of the next three; they go into the certificate.
Optional, for the registration certificate wallets are shown (privacy policy, information page, data-protection supervisory authority).
With this box, wallet sign-ins through the gateway for this client carry this relying party’s own registration certificate, naming this site as intermediary; the wallet authenticates this site by its access certificate. Needs this site’s own verifier certificate from this CA. Without a registration, the client’s sign-ins work as before with this site as the relying party.
Issue a certificate
This site’s verifier certificate
Issues an access certificate for this site’s own OpenID4VP verifier (key made and kept on this server). Wallet requests started with registrar=codeb are then signed with it; wallets must trust this CA.
This site’s issuer certificate
Signs this site’s credential issuer metadata for wallets that ask for the signed form (application/jwt). Issued for the same registration as the verifier certificate above; key made and kept on this server. A certificate from another CA that is already installed is never replaced.
Registration certificate signer
Signs the registration certificate (ETSI TS 119 475, rc-wrp+jwt) that wallet requests started with registrar=codeb carry in verifier_info. It is built from this site’s registration above (the one the verifier certificate was issued for). Key made and kept on this server; used for nothing else.
CodeB Playground
Test organisations that people register themselves on the playground page. Nothing about them is verified; their certificates carry the playground marker and last 30 days at most. They are listed here and not in the register below.
| Test organisation | Account | Status | Certificates | Actions |
|---|
Register
| Relying party | Identifier | Status | Certificates | Actions |
|---|
Certificates
| Serial | Relying party | Valid until | Status | Actions |
|---|