Configuring the Adaptable CA object

As with other Venafi CA drivers, you should review the Getting started: automating certificate enrollment and provisioning section before setting up the Adaptable CA driver.

NOTE  Before you attempt to create CA template, device, or application objects, you must enable the create permission under the folder where you want to create the new object. For more information, see Permissions overview.

To create and configure a new Adaptable CA template object

  1. From the TLS Protect menu bar, click Policy Tree.
  2. From the Tree drop-down menu, click Policy.
  3. In the Policy tree, select the folder where you want to create the CA Template object, and then click Add.
  4. Click CA Template, then select Adaptable to create it.
  5. In the CA Name box, type a name for the new Adaptable object.
  1. Under Connection, do the following:

    1. Using the Username Credential and Certificate Credential fields, select one or both credentials.

      If your organization requires two-factor authentication, then specify both credentials.

    2. (Optional) (Conditional) If you need to select another credential, then from the Secondary Credential field, select a username, certificate, password, or CyberArk credential object.

      TIP  Use this option to avoid having to hard code additional credentials in your script or having to utilize other solutions outside of Trust Protection Platform.

  2. Select your Windows PowerShell script from the PowerShell Script list.

    Scripts contained in the Program Files\Venafi\Scripts\AdaptableCA folder appear in this list.

  3. To verify that functions are working, click Validate.

    What does Validate do?Closed When you click Validate, Trust Protection Platform verifies if the required PowerShell functions are present in the selected PowerShell script and then executes the Test-Settings function. In addition, if you had obtained the testing utility from Venafi Support (see Adaptable CA prerequisites), then the test script would also write a file for every method that gets called to show what data is getting returned. For example, if you had set the certificate credential, Trust Protection Platform would have generated a text file showing the data that was sent to the test script:


  4. Under Options, configure certificate replacement (sometimes called reissuance) by doing the following:

    1. In the Renewal Window (days) field, specify how many days prior to the expiration of an existing certificate that the certificate should be renewed.

      Any certificates that fall outside of the renewal window are handled through a replacement or reissuance.

    2. To enable renewal without changing the original expiration date, check Allow Reissuance.
    3. (Optional) Select When script is updated, fix related certificate errors if you want Trust Protection Platform to fix certificates affected by changes to the associated PowerShell script.

      For more information about how changes to scripts can affect certificate enrollment, see Protecting against unapproved changes to Adaptable CA scripts.

  5. (Optional) If you want to enhance troubleshooting capabilities of your Adaptable Flow, select the Enable Debug Logging check box.

    For information about how enabling this option works with the PowerShell script, see in the Adaptable Flow PowerShell script reference.

  6. Click Add / Remove to select the custom fields you want to include.

    Data related to the custom fields you select is passed using the functions defined in the PowerShell script.

    For more information about custom fields, see Working with custom fields.

  7. (Optional) If your application will connect to the VenafiWeb SDK, then complete the WebSDK OAuth Token Configuration settings:



    OAuth Token Application IDEnter the application ID of the API application integration you should have created previously, as described in Adaptable CA prerequisites.
    OAuth Token Credential

    Select the username credential of the service account that has been granted access to the Client ID of the API Application. See Adaptable CA prerequisites.

    In this context, the username credential identifies the user (identity) for whom the token is being requested. It also verifies whether you have the required permissions within your organization to enable the script to authenticate as the selected user. This security measure prevents users from impersonating another user.

    OAuth Token Scope

    (Optional) Enter one or more of the scopes assigned to your API application. For example, Certificates: Manage. Leave this field blank if you want to include all defined scopes.

    To learn more about scopes and restrictions, see Scopes for token.

    NOTE  If your application is not connecting to the Web SDK, leave all of these fields blank.

  8. (Conditional) If your script includes customized fields, enter the desired static text or macro commands.

    Refer to the sample in the topic, Example: creating a ServiceNow incident for expiring certificates.

    For more information about Venafi's macros, see Macro commands.

  9. When you're finished, click Save.
  10. IMPORTANT  If you make changes to the PowerShell script used by an Adaptable CA, you must open the corresponding CA object and click Save to force the driver to re-read the script. Typically, the updated script becomes active in less than 60 seconds after saving the channel object.

  11. Click Save.

What's next?

After you create a CA object, you can select it from the Policy tree, and then view important information and manage various settings.

  • Click the General tab to view and modify log and permissions settings.

    • Click the Log sub-tab to view any logged events that are triggered by the template object.

      IMPORTANT  You must have the Read permission to view the Log tab.

      For more information about options found on the Log tab, see Viewing log events.

    • On the Permissions sub-tab, you can configure the users or groups to whom you want to grant permissions to the new template object.

      Consider managing object permissions via parent objects so that you can take advantage of inheritance. For more information, see Permission inheritance and flow down.

Related Topics Link IconRelated Topics