Iteration 5¶

Target: User-provided private key, List filtering and pagination, Robots

Tasks¶

User-provided key¶

The application shall provide a possibility to provide his own private key or to let the application generate a key with a user-selected password.

Req: FR 1.1.2, 1.1.3, 1.1.4, 2.1.2, 2.1.3, 2.1.4

GUI¶

• Web GUI - The certificate creation page shall contain a new checkbox "Generate key pair".
• Web GUI - The certificate creation page shall contain a text field to specify a password for the private key.

Core¶

• Rest API shall enable a PEM encoded PK to be specified within the request for creating a certificate.
• Rest API shall enable a password to be specified within the request for creating a certificate.
  • If a password is present in the request and the private key is not present, the server generates a key protected by the given passphrase.
  • If a password is not present in the request and the private key is present, the server uses the given key. However, the server must do a check if the private key is
    not protected by a passphrase -> if yes, an error response is returned.
  • If both password and key are not present, the server generates a key without passphrase protection.
  • If both password and key are present, the server uses the given key and checks whether the given passphrase decyphers the key-> if not an error response is returned.

Validity check¶

The application shall provide an endpoint to verify the validity of the selected certificate.

GUI¶

• Web GUI - The certificate details page provides an indication of certificate validity.

Core¶

• Rest API shall provide an endpoint /api/certificate/{id}/status to query certificate status
• The application shall distinguish three types of status: valid, expired, revoked