Akeyless integrates with Venafi to provide certificate automation. Akeyless can be used for Venafi Trust Protection Platform (TPP) and Venafi Cloud to ensure compliance with enterprise policies and consistency with industry standards.
You no longer need to manually issue new PKI certificates, and you can dynamically retrieve PKI certificates.
Either Akeyless or Venafi can act as the certificate issuer.
Venafi Issuer: The certificate is signed by Venafi’s intermediate Certificate Authority (CA). The issued certificate is saved on Venafi and in the Akeyless Vault Platform. The certificate issuing policy template is pulled from the Venafi Zone configuration.
Akeyless Issuer: The certificate is signed by a CA key from the Akeyless Vault Platform created by the user. In addition, the issued certificate is saved in the Akeyless Vault Platform as a secret and exported to Venafi for monitoring.
A certificate can be requested based on a Common Name (CN) or via a Certificate Signing Request (CSR). Both these methods fully support Cert Manager.
The outcome artifacts of certificate issuance, including the certificate, private key, and certificate chain, are saved in the Akeyless Vault Platform as a static secret in a configurable location.
Certificate Automation settings
Venafi API Key - The API Key to use when connecting to a Venafi Cloud environment.
Venafi Username - The username to use when connecting to a Venafi Trust Protection Platform environment.
Venafi Password - The password to use when connecting to a Venafi Trust Protection Platform environment.
Venafi Base URL - Base URL of the TPP environment or Venafi cloud environment.
Venafi Zone - The zone to use when issuing new certificates (policies will be pulled from the provided zone).
Sign Using Akeyless PKI - Determines whether to use Akeyless as an issuer.
Signer Key Name - The signer key to use as the issuer, must be a valid RSA 2048/4096 key with a certificate (Required when using Akeyless PKI, must already exist in Akeyless Vault).
Allowed Domains - A list of allowed domains when requesting a new certificate (
Allow Subdomains - Whether to allow subdomains (
User TLL - The TTL of requested certificates (
default: 90 days).
Certificate Chain Order-Root First - Where to place the root certificate in the certificate chain (
default: root first).
Store Private Key in Akeyless Vault - Whether to keep the generated private key in Akeyless Vault as a static secret (Not relevant when using TPP, or generating a certificate using CSR) (
Artifacts Location - The location to place the generated artifacts in Akeyless Vault (
Updated almost 2 years ago