Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.futurex.com/llms.txt

Use this file to discover all available pages before exploring further.

This section covers how to configure the Futurex Adaptable CA PowerShell driver and Custom Fields PowerShell script.

​
Install the Futurex Adaptable CA driver

1
Open the PowerShell application.
2
Go to the directory containing the extracted Venafi Adaptable CA endpoint files.
3
Run the Futurex Adaptable CA PowerShell script by executing the following command:
Shell
.\Futurex KMES CA.ps1
This sets all required configuration parameters to use the Futurex Adaptable CA driver inside Venafi TPP.

​
Run the Custom Fields PowerShell script

The FuturexCreateCustomFields.ps1 script defines three custom fields in Trust Protection Platform. These are used for defining the approval group within the CryptoHub that will control approvals of issuance requests, defining the validity period, and defining X.509 extension profiles. X.509 extension profiles allow users to define the type of certificate being deployed. This must match an option defined for the relevant issuance policy. These fields are optional and can provide additional levels of granular control over Venafi policies for certificate attributes and issuance structure.
1
Open the PowerShell application.
2
Go to the directory containing the extracted Venafi Adaptable CA endpoint files.
3
Open FuturexCreateCustomFields.ps1 in a text editor and change the following variables to ones appropriate for the Venafi TPP installation. Refer to this Venafi Docs article for instructions on getting a token using browser-based authentication.
Text
# Configuration
$SdkUri = "<VENAFI TRUST PROTECTION PLATFORM HOSTNAME OR IP>"
$SdkToken = "<VENAFI TRUST PROTECTION PLATFORM TOKEN>"
4
After you make the preceding changes, run the script with the following command in PowerShell:
Shell
.\FuturexCreateCustomFields.ps1
The script only needs to be run once on each server running Venafi TPP, regardless of how many CryptoHub’s or issuance policies are defined.