Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions content/en/docs/configuration/venafi.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,24 @@ of the connection parameters are slightly different.

> **Note**: You *must* allow "User Provided CSRs" as part of your TPP policy, as
> this is the only type supported by cert-manager at this time.
>
> More specifically, the valid configurations of the "CSR handling" are:
>
> - "User Provided CSRs" selected and unlocked,
> - "User Provided CSRs" selected and locked,
> - "Service Generated CSRs" selected and unlocked.
>
> When using "Service Generated CSRs" selected and unlocked, the default CSR
> configuration present in your policy folder will override the configuration of
> your Certificate resource. The subject DN, key algorithm, and key size will be
> overridden by the values set in the policy folder.
>
> With "Service Generated CSRs" selected and locked, the certificate issuance
> will systematically fail with the following message:
>
> ```plain
> 400 PKCS#10 data will not be processed. Policy "\VED\Policy\foo" is locked to a Server Generated CSR.
> ```

In order to set up a Venafi Trust Protection Platform `Issuer`, you must first
create a Kubernetes `Secret` resource containing your Venafi TPP API
Expand Down