6.3.1.2. Certificate Token

Starting with version 2.3 privacyIDEA supports certificates. A user can

  • upload a certificate request,

  • upload a certificate or

  • he can generate a certificate request in the browser.

privacyIDEA does not sign certificate requests itself but connects to existing certificate authorities. To do so, you need to define CA Connectors.

Certificates are attached to the user just like normal tokens. One token of type certificate always contains only one certificate.

If you have defined a CA connector you can upload a certificate signing request (CSR) via the Token Enroll Dialog in the WebUI.

../../_images/upload_csr.png

Upload a certificate signing request

You need to choose the CA connector. The certificate will be signed by the CA accordingly. Just like all other tokens the certificate token can be attached to a user.

6.3.1.2.1. Generating Signing Requests

You can also generate the signing request directly in your browser.

Note

This uses the keygen HTML-tag that is not supported by the Internet Explorer!

../../_images/generate_csr1.png

Generate a certificate signing request

When generating the certificate signing request this way the RSA keypair is generated on the client side in the browser.

The certificate is signed by the CA connected by the chosen CA connector.

../../_images/generate_csr2.png

Download or install the client certificate

Afterwards the user can install the certificate into the browser.

Note

By requiring OTP authentication for the users to login to the WebUI (see login_mode) you can have two factor authentication required for the user to be allowed to enroll a certificate.