- Enable the required Host API commands.
- Create KMES credentials for Venafi TPP.
- Create a signing approval group.
- Create an issuing CA.
- Add an issuance policy.
- Allow user-defined extensions for X.509 Extension Profiles (optional).
Enable the required commands
Because Venafi TPP connects to the Host API port on the KMES, you must define which Host API commands to enable. To set the allowed Host API commands, complete the following steps:Go to Administration > Configuration > Host API Options and enable the following commands:
| Command | Description |
|---|---|
| RAGX | Retrieve Request (X.509 CSR) |
| RASX | Manipulate Signed Request |
| RAUX | Upload Request (X.509 CSR) |
| RAYX | Approve Requests |
| RKLO | Login User |
| RKRK | Retrieve Generated Keys |
Create KMES credentials for Venafi TPP
Venafi TPP supports two options for user credential management. The single-user role option establishes one user per issuance policy that is permitted to submit certificate issuance requests, approve or deny requests, and revoke certificates. The dual-user role option establishes two users per issuance policy, with one permitted only to submit certificate issuance requests and one permitted only to approve or deny issuance requests or revoke issued certificates. For a greater degree of administrative separation and adherence to principles of role-based access control, we recommend using the dual-user method. Select the following dual-user or single-user role and identity creation methods and follow the steps:Dual-user role option (recommended)
Perform the following steps to set up a dual-user role to control certificate requests, approval, and revocation. One user is responsible for submitting certificate issuance requests, while the other is solely responsible for approving, rejecting, and revoking certificates.On the Info tab of the Role Editor window, specify a name for the role and set the number of logins required to
1.On the Permissions tab, enable the following permissions:
| Permission | Subpermission |
|---|---|
| Certificate Authority | Export, Upload |
Go to Identity Management > Identities, right-click anywhere in the window, and select Add > Client Application.
On the Info tab of the Identity Editor window, select Application for the storage location and specify a name for the identity.
On the Authentication tab, remove the default API Key authentication mechanism, add the Password authentication mechanism, and configure it.
Single-user role option
Perform the following steps to set up a single-user role to control certificate requests, approval, and revocation.On the Info tab of the Role Editor window, specify a name for the role and set the number of logins required to
1.On the Permissions tab, enable the following permissions:
| Permission | Subpermission |
|---|---|
| Certificate Authority | Export, Upload |
| Signing Approval | Approve |
Go to Identity Management > Identities, right-click anywhere in the window, and select Add > Client Application.
On the Info tab of the Identity Editor window, select Application for the storage location and specify a name for the identity.
On the Authentication tab, remove the default API Key mechanism, add the Password authentication mechanism, and configure it.
Create a signing approval group
To enable certificate signing approval workflows on the KMES Series 3, perform the following steps to create a signing approval group:Remember the group name because you use it to configure the Adaptable CA driver configuration in a later section of this guide.
Create an issuing CA
Perform the following steps to create an issuing CA certificate tree on the KMES Series 3:In the Certificate Authority window, enter a name for the certificate container, select the Venafi Adaptable CA role in the Owner group drop-down menu, and select [ OK ].
On the V3 Extensions tab, select the Certificate Authority profile and select [ OK ] to create the certificate.
Add an issuance policy
Perform the following steps to add an issuance policy:On the Basic Info tab of the Issuance Policy window, set an alias for the issuance policy (optional), set the desired number of approvals required for certificate requests, and set the hashes that you want to allow.
On the X.509 tab, perform the following actions:
- Select the Allow CSR uploads checkbox.
- Set the Default approval group to the approval group you created.
- If you set the number of required approvals to
0, you must select the Allow self approval checkbox. Otherwise, leave it unchecked. - Add at least one Extension Profile. If you are not using the Custom Fields PowerShell script, you must define exactly one extension profile here.
If you set the number of approvals required to 0, you must set Anonymous Signing security usage on the issuing CA certificate. To do so, right-click on the issuing CA certificate and select Change Security Usage. Then, in the drop-down menu, select Anonymous Signing and select [ OK ] to save the changes.
(Optional) Allow user-defined extensions
The Allow User-Defined Extensions option is disabled by default. This is by design to maintain a more secure configuration. Only enable it if your workflow requires users to define custom extensions.
Enable Allow User-Defined Extensions
Perform the following steps to enable the Allow User-Defined Extensions option for the X.509 v3 extension profiles you plan to use with Venafi Adaptable CA:Add Subject Alternate Names
Perform the following steps to add Subject Alternate Names (SANs) to the X.509 v3 extension profiles you plan to use with Venafi Adaptable CA:Select [ Add ], select the Subject Alternate Name extension type in the drop-down menu, and select [ OK ].

