Your key pair is generated in this browser. A certificate signing request is sent to the entityOS mTLS issuer, signed by the private CA, and returned as a ready-to-install .p12 — one single-use access code per certificate.
Provided by your administrator. Works once.
Embedded as the Subject Alternative Name in your certificate.
Password:
Your .p12 file has been downloaded automatically. If not, download it here.
Optional
Your certificate was issued by the entityOS mTLS private CA. The CA certificate is bundled inside the .p12; download it separately if a tool needs the CA on its own.
macOS: Double-click the downloaded .pem → Keychain Access → expand Trust → set When using this certificate to Always Trust. Windows: Double-click → Install Certificate → Place in Trusted Root Certification Authorities. macOS: Double-click the downloaded .pem → Keychain Access → expand Trust → set When using this certificate to Always Trust. | Windows: Double-click → Install Certificate → Place in Trusted Root Certification Authorities.
Under the hood
Your browser uses the Web Cryptography API (window.crypto.subtle) to generate an RSA-2048 key pair. Once installed, the private key lives in your device's certificate store.
The browser constructs a PKCS#10 CSR containing your public key, a unique common name, and your email address as a Subject Alternative Name, then sends it with your single-use access code.
The issuer verifies the CSR signature, checks the access code is valid and unused, and signs your public key with the entityOS mTLS CA — producing an X.509 client certificate (clientAuth) valid for 365 days by default. The code is marked used and an issuance record (serial, fingerprint, public certificate) is written to encrypted S3. The private key is never stored.
The signed certificate, the CA certificate and your private key are packaged into a PKCS#12 (.p12) protected by a random password, and the file downloads automatically. Install it once and your browser presents it on every connection to the mTLS-protected load balancer.