TLS client certificates
A site can ask the browser to present a certificate stored on the computer.
In one line
Can ask your browser to show a certificate stored on your computer
A site can ask the browser to present a certificate stored on the computer.
Certificates identify a person or company. The browser asks which cert to send; used in banks and enterprise.
What it can and can't do
What the user does: You open a bank or company site and pick a certificate in the box that appears
It can
- Ask you to choose one certificate from those on your device
- Receive the certificate you choose to prove who you or your company are
- Sign you in to a bank or work site without a password
It cannot
- Pick a certificate for you without your choice, unless you set the browser to auto choose
- Get the private key; it stays on your device or security card
- See certificates you did not choose to send
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1.0 | 2008-12-11 | None |
| Edge | Supported | 1.0 | Not listed | None |
| Firefox | Supported | 1.0 | 2004-11-09 | None |
| Safari | Supported | 1.0 | 2003-06-23 | None |
| Safari on iPhone | Supported | 1.0 | 2007-06-29 | None |
| Chrome on Android | Supported | 1.0 | Not listed | None |
| Samsung Internet | Supported | 1.0 | 2013-04-27 | None |
How a site asks for it
| API | TLS CertificateRequest during handshake; browser certificate chooser |
| How access is granted | prompt |
| What the user sees | Browser or OS certificate picker |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: A site can ask the browser to present a certificate stored on the computer.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
subject DN | string | None | certificate defined | Not listed |
issuer | string | None | CA name | Not listed |
Technical limits
- Page cannot read cert store
- Chooser shown at TLS layer
- Auto select via enterprise policy
The story
What it is
The browser can offer a digital ID card stored on your computer when a site asks.
For you
A box may pop up asking which certificate to use, or it picks one for you. There is no password box. You mostly see this at work, school or a government service.
For makers
Makers use client certificates for very strong machine and person checks, such as a bank or an internal company tool. It proves the device is one the company issued before the site loads.
Where you see it
| Type | Example | Apps |
|---|---|---|
| enterprise | A company intranet only opens on laptops that carry a certificate from IT, so a stolen password alone does not get in. | None named |
| banking | A business bank portal asks for a certificate stored on a smart card or token before it shows balances. | None named |
| security | A government tax or health web service uses a national ID certificate to prove who is filing. | None named |
| developer | An engineer reaches a staging server or code tool that only accepts browsers with the right certificate. | Cloudflare Access |
| games | An online gaming tournament admin panel is limited to organizer laptops with certificates, so only staff can change brackets. | None named |
| analytics | A security team logs which certificate connected to spot an unusual device. | None named |
Risks
- Certificate reveals identity to site
- Hard to set up and move
Good uses and abuse
Legitimate uses
- Mutual TLS in enterprise
Known abuse
- Identity linking across sites if the same cert is used
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 1999, Chrome 1: Client cert support from early TLS
Sources
How well checked: Inferred from related behavior.