Open the signing request
Someone sends you a PDF to sign, or you create a request yourself on the signing page. Scan the QR code (or open the e-mailed link) with CodeB Wallet.
CodeB Wallet · NFC · eID card
A government-issued eID card holds two keys: one for signatures and one for authentication. CodeB Wallet reads the card over NFC, so you can sign PDFs with it and sign in to websites, with the card’s PIN and the card’s own certificates.
PAdES (ETSI EN 319 142) · B-T · B-LT · B-LTA · RFC 3161 time stamps · OCSP / CRL · OpenID Connect · NFC
Closed beta, in testing. Not certified.
urn:codeb:acr:eidcard. The card certificate must chain to an issuing CA installed on this server and must not be revoked.The card signs, the server builds the PDF signature.
Someone sends you a PDF to sign, or you create a request yourself on the signing page. Scan the QR code (or open the e-mailed link) with CodeB Wallet.
CodeB Wallet opens the card with its card access number and reads the signing certificate. The server prepares the PDF signature and sends the phone only a 32-byte hash.
The card signs the hash with its signing key inside the chip. The PIN and the key never leave the card.
The server embeds the signature and adds a time stamp, the certificate’s validation data and a document time stamp as far as they can be had (PAdES B-T, B-LT, B-LTA). It checks the signed PDF before the next signer gets their turn.
One challenge, one signature, signed in.
On the sign-in page of this site (or of a website that signs in through it), choose the eID card. The page shows a QR code; on the phone itself, a button opens the app.
The app fetches a one-time challenge for exactly this sign-in.
The card’s authentication key signs the challenge together with the website address, the session and the time, so the signature cannot be used anywhere else.
The server checks the signature, that the card certificate chains to the issuing CA certificates installed on this server and that it is not revoked (OCSP or CRL). The browser continues signed in.
Only a 32-byte hash travels to the phone and only the card’s signature comes back. The document is never sent to the phone for card signing.
The card signs inside its chip after you enter the PIN. Neither the PIN nor a key ever reaches this site or the app’s storage.
A card signature session lives 5 minutes and belongs to your account and to the app’s key. A sign-in challenge lives 2 minutes and names the website, the session and the time.
Sign-in checks the chain to the installed issuing CAs and the revocation status; if OCSP and CRL cannot be reached, the sign-in is refused rather than allowed.
Every signed PDF is validated before the request moves on: one valid signature over exactly the document, no hidden changes.
No third-party scripts, no analytics. Only identifiers and outcomes are logged, never document content.
Only if the signing certificate on your card is a qualified certificate (most national eID cards with a signature function have one). The server checks the certificate; for a request that asks for a qualified signature, a card certificate that does not state one is refused. CodeB itself is not a qualified trust service provider and adds no qualification.
An eID card can sign a hash but cannot build a PDF signature. The server prepares the PDF signature, the card signs only its hash, and the server embeds the card’s signature. The PDF stays on the server.
As high as the time-stamp and validation services allow: B-T with a signature time stamp, B-LT with OCSP responses or CRLs, B-LTA with a document time stamp. The result says which level was reached and why a higher one was not.
Government-issued eID cards that CodeB Wallet can read over NFC and whose certificates chain to issuing CA certificates installed on this server; this site is set up for the Maltese eID card. The card certificate must also pass the revocation check (OCSP or CRL).
Your given name and family name from the card certificate and a pseudonymous account identifier. The national ID number is not put into ID tokens or userinfo, the PIN never leaves the card, and the site claims no level of assurance for this sign-in.
Yes. Link the card to your account once: sign in, open the eID card page with link=1 within 10 minutes, read the card and confirm in the browser that the name from the card is yours. After that the card signs you in to that account.
Yes. A signing request can invite people by e-mail to sign one after another; each signer can use an eID card, another signature card or the signing service.
No. The PDF signatures follow PAdES (ETSI EN 319 142) and the sign-in uses OpenID Connect, but the software is not certified.
Signing requests by QR code, several signers, e-mail invitations.
The sign-in page with the QR code.
How the server finishes the PAdES signature, for developers.
eidcard-start, -challenge, -response and -poll.
Write to us about eID card signatures, sign-in with eID cards and signing requests. Testers for CodeB Wallet are welcome too.