Identity & Access Management with PQC
Migrate enterprise IAM systems to quantum-safe cryptography: JWT/SAML token signing, Active Directory, LDAP, vendor roadmaps, and zero trust identity architecture.
Why this matters: Public-key signatures in JWTs, SAML assertions, and OIDC tokens may eventually need post-quantum algorithms; HMAC-signed tokens use symmetric cryptography and have a different quantum risk. Track vendor support by feature: Microsoft now targets a full quantum-safe Entra authentication transition by 2033, while token-signing algorithm availability remains a separate implementation question.
Start here: Migrate a SAML or JWT signature to ML-DSA in the Token Migration step: the signature sizes and header changes are compared on the same token.
For your role
- Executive / Business Leader
- Audit eight IAM components by quantum risk and migration priority, and score Okta, Entra, PingFederate and ForgeRock across PQC dimensions: the vendors are on different timelines you have to track.
- Developer / Engineer
- Migrate SAML and JWT signing to ML-DSA and compare signature sizes and headers, then simulate translating a PQC SAML assertion to classical RSA for legacy relying parties.
- Security Architect
- Design the phased roadmap across the five identity pillars in Step 5, with the AD, OpenLDAP and Entra vulnerability analysis in Step 3 behind it.
- Researcher / Academic
- The vendor scoring across PQC dimensions and the directory vulnerability analysis with HNDL exposure are explicit and repeatable; the token-migration step gives the signature sizes.
- IT Ops / DevOps
- The eight-component audit in Step 1 orders the work, and the legacy-translation step in Step 6 is what keeps old relying parties working during the cutover.
- Curious Explorer
- Every login token your systems issue is signed; the module shows which parts of an identity system a quantum computer would break and in what order to fix them.
Identity and Access Management relies on cryptography at every layer. From and token signing to channels and certificates, a quantum computer running can break the RSA and ECDSA signatures that protect every identity assertion in your enterprise.
Adversaries are recording encrypted network traffic today. When a Cryptographically Relevant Quantum Computer (CRQC) becomes available, they can decrypt captured Kerberos PKINIT exchanges and the TLS sessions that carry identity traffic. Signed tokens (JWT, SAML, OIDC) are signed, not encrypted: breaking a signing key later reveals nothing that was hidden. The risk is that a broken signing key lets an attacker forge tokens. NIST IR 8547 ties harvest now, decrypt later to encrypted data and says the authentication algorithm may be transitioned at a different time.
Tickets are encrypted with symmetric keys. The quantum-exposed step is PKINIT (RFC 4556), which delivers the AS reply key by Diffie-Hellman or RSA encryption. Breaking it for a captured exchange yields that client's reply key and TGT session key, which let an attacker act as that one client until the ticket expires. Forging tickets for any account, a Golden Ticket, additionally needs the KRBTGT long-term key, which a PKINIT break does not give.
SAML assertions are signed. A quantum computer that breaks the signing key could forge assertions that grant federated access to all relying parties; long-lived assertions (hours to days) lengthen the window. This is a forgery risk, not harvest-now-decrypt-later.
JWTs are signed and commonly cached and reused for their full validity period. A forged JWT is accepted while the verifier trusts the signing key, so the risk is forgery, not harvest-now-decrypt-later. Refresh tokens (weeks/months) give the longest window; access tokens (1h) a shorter but still significant one.
OIDC ID tokens carry identity claims and are signed, not encrypted. A quantum computer that breaks the issuer signing key could forge identity assertions to all OIDC relying parties that trust the issuer. This is a forgery risk, not harvest-now-decrypt-later.
A public-key-signed access token may be forged if its signing key is broken; token lifetimes and refresh-token behavior vary by issuer, client type and policy. Treat token forgery, bearer-token theft, and TLS HNDL as separate risks.
| Algorithm | Sig Bytes | Sign Time | Status |
|---|---|---|---|
| RS256 | 256 B | 1ms | Vulnerable |
| ES256 | 64 B | 0.5ms | Vulnerable |
| ML-DSA-44 | 2,420 B | 1.8ms | Quantum-Safe |
| ML-DSA-65 | 3,309 B | 2.1ms | Quantum-Safe |
| ML-DSA-87 | 4,627 B | 3ms | Quantum-Safe |
Related Resources
Products shown here are a representative selection — not an exhaustive list. For the full vendor landscape with PQC readiness status, visit the Tools & Products tab in this module or browse the Migrate catalog →
Audit IAM crypto, migrate JWT signing, analyze directory services, and design a zero trust PQC roadmap.
Check off all sections and mark this reading done.
Related modules
In the Industry Landscape
Check your understanding
15 questions on Identity & Access Management with PQC, each with its answer and the reason.
Take the quizNext step
Practice it: Multi-Algorithm SigningMulti-Algorithm Signing is the hands-on version of this module: the same ideas, run in your browser.
Production Tool Capabilities & Verification ChecklistIdentity & Access Management (IAM) Architects & Workforce Security Leads
Capabilities to require in your production tools:
- OIDC / OAuth 2.0 / SAML 2.0 Identity Provider (IdP) token and assertion signing with `ML-DSA-65` and hybrid TLS 1.3 transport.
- FIDO2 / WebAuthn and PIV / smartcard hardware authenticator roadmap and enrollment support for post-quantum public-key credentials.
- Kerberos PKINIT and Active Directory Certificate Services (ADCS) migration paths from RSA/ECDSA to PQC/hybrid certificates.
How to evaluate in your environment
Test SAML/OIDC federation login flows with PQC-signed tokens and oversized XML/JSON payloads across browser and reverse-proxy stacks.
Production evidence to collect
IdP metadata/JWKS export, federation login trace, and smartcard/authenticator capability assessment.
Completing this Hub module and its browser-based sample exercises teaches the technical and governance decision criteria for your role; it does not test, validate, or certify your deployed production systems.
Record evidence for your environment
Identify the tested build and configuration. Use reference IDs for observations. For a proposed exclusion, record the system boundary or rule and why it excludes this build.
Evidence missing. 0 of 3 requirements have a reference or scope rationale.
Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.