Protocols
Saved & recent

Certificate authority

Also called: CA, certification authority, trust chain

A certificate authority issues and signs certificates under a stated policy. A relying application accepts a certificate only if its checks establish an appropriate path to a trust anchor it already trusts. A self-signed root does not become trustworthy merely by signing itself.

For example, a browser may validate a server certificate through an intermediate CA to a root in its trust store. Signatures establish links in that chain, while validity and constraints still matter. Public and private organizations can operate CAs; accepting an organization’s private CA is a separate trust decision.

Read first
Certificate
Related
Certificate, Mutual TLS
Further reading
RFC 5280 — Internet X.509 Public Key Infrastructure Certificate and CRL Profile
trusted root CA trust anchor intermediate CA issuer certificate server certificate leaf certificate configured trust store issues issues validate toward trusted root client validator trust configured in advance
Issuers sign certificates down the chain; the client validates a path toward a root already in its trust store. Validity, names and constraints still need checking. A root’s self-signature does not create trust.

View in the full Protocols collection