Certificates & Proofs / PKI Workshop

What you will do: Work through five steps: generate a CSR, create a Root CA, issue a certificate by signing the CSR with that CA, parse the certificate, then build a CRL.

Worked example: Generate a CSR for example.com with a new RSA 2048-bit key, self-sign a Root CA, press Sign Certificate to issue the leaf, then Parse Details shows its subject and issuer.

Runtime and privacy: The cryptographic exercise runs in this browser. Review the site privacy terms before entering sensitive material; use synthetic inputs for learning and evaluation.

Browse all Crypto Lab tools · Learn with PKI

For your role

Developer / Engineer
Step 1 generates a key and a CSR (choose the key source and a profile), Step 2 creates a root CA, Step 3 issues the certificate, Step 4 parses it and Step 5 revokes it with a CRL: the Console Output is the OpenSSL you would run.
Security Architect
Pick a profile in Select Profile and read the constraints it applies, then compare the parsed certificate in Step 4: the fields and sizes are what a PQC key changes in a chain.
Researcher / Academic
Use the Console Output at each step to reproduce the CSR, CA, issuance and CRL outside the browser.
IT Ops / DevOps
Run the five steps once with the default RSA key to see the full issue-and-revoke cycle, then note the Step 5 CRL: it is the artefact your revocation distribution has to carry.
Curious Explorer
Follow the five steps in order: you make a request, create an authority, get a certificate issued, read what is inside it, and revoke it — the whole life of a certificate in one sitting.

Browser learning sandbox — keys and certificates are generated in-memory via OpenSSL WASM and must not be used in production. Verify CA policy, HSM key protection, and chain validation with your production PKI tools.

Step 1: Generate CSR

Create a Certificate Signing Request using a key pair.

01|KEY CONFIGURATION

Generate new keypair • Select algorithm • Choose key size

Private Key Source:

02|SELECT PROFILE

Load industry template • Apply standards • Set constraints

CSR Profile

Without a profile the CSR will contain only the Subject DN — no extensions (SAN, EKU, keyUsage). Modern CAs require a subjectAltName per CAB Forum BR. Select a profile to inject the correct extensions for your use case.

3BUILD CSR ATTRIBUTES

Define Subject DN • Add Extensions • Configure Request

UseTypeNameValueRec. / Desc.
SubjectRDN
Common Name
Presence requirement: mandatory
The fully qualified domain name (FQDN) of your server.
SubjectRDN
Organization
Presence requirement: recommended
Legal name of the organisation requesting the certificate.
SubjectRDN
Country
Presence requirement: recommended
Two-letter ISO 3166-1 country code of the organisation.
No SAN loaded. Modern TLS certificates require a subjectAltName (SAN) extension per CAB Forum Baseline Requirements. The CN alone has been deprecated for TLS hostname validation (not sourced in the Library). Select a profile above to load SAN and other required extensions automatically.

4SIGN & CREATE CSR

Hash request data • Sign with private key • Encode to PEM

Console Output

Next in sequence

Cert Capacity Calculator

Estimate certificate-related TLS payload and annual leaf issuance storage for classical and PQC chains (no CPU prediction).

Production Tool Capabilities & Verification Requirements

What this sample check establishes: Builds and verifies X.509 v3 certificate chains signed with post-quantum algorithms (`ML-DSA-44/65/87`, `SLH-DSA`) using OpenSSL 3.6 WASM.

Browser sandbox limitation (non-certification boundary): In-browser CA uses ephemeral keys in WASM memory; it does not provide HSM root key protection, CRL distribution points, or audited CA ceremony controls.

What to require and test in your production tools:

  • CA software that supports RFC 9881 (`ML-DSA`) and, where needed, RFC 9909 (`SLH-DSA`) X.509 OIDs; check each product (for example EJBCA and DigiCert Trust Lifecycle Manager list both, Microsoft AD CS and AWS Private CA list ML-DSA).
  • Root and Issuing CA private keys in a FIPS 140-3 validated HSM (Level 3 or higher where your CA policy requires it), with multi-person activation.
  • Automated CRL/OCSP and short-lived certificate issuance pipelines validated for multi-kilobyte PQC certificate chains.

Try it

  1. 1. Predict before you run it.
  2. 2. Run or change the tool above.
  3. 3. Explain what the result shows.

After Step 3 issues the certificate, what does Step 5 produce for the Root CA?

A CSR verifies against its own public key and requests gateway.example.test. What should the issuer do before approving that name?

Next step

Turn it into a plan: Infrastructure Modernization Planner

This tool practises the PKI module, phase 6 (Infrastructure & Performance); Infrastructure Modernization Planner produces a deliverable of that phase.

Next in Certificates & Proofs