Configuring an Adaptable Application object

To create and configure a new Adaptable Application object

1. From the TLS Protect menu bar, click Policy tree.

2. In the Policy tree, select the device object to which you want to add the new application object, and then click Add > Application, and then select Adaptable Application.

3. When the new application object page appears, then under Status, clear the Processing Disabled checkbox.

   When checked, this option disables provisioning of the certificates installed on the current application. This means that Trust Protection Platform does not attempt to install, renew, process, or validate certificates on the application.

4. (Optional) In the Device Certificate box, click to select and associate a certificate with the new application.

   NOTE  If you don't have a certificate ready, you can do this later or you can do it on the certificate's Association tab.

   To associate a certificate with the current application, you must have write permissions to the application object and either write or associate permissions to the certificate object.

   For detailed information on associating a certificate with an application, see Associating a certificate with an application object.

5. Under General, do the following:

   1. In the Application Name field, type a name for the new application.

   2. (Optional) In the Description field, type a description for the purpose of the application.

      A strong description can help to provide context for other administrators who might need to manage the new application.

   3. In the Contacts field, select user or group identities you want assigned to this application object (or choose the Use policy value to configure contacts using a policy).

      Default system notifications are sent to the contact identities. The default contact is the master administrator.

      TIP  If the Identity Selector dialog is not populated when it first opens, enter a search query to retrieve the Identity list. The administration console does not automatically display external users and groups. You must first enter a search string so Trust Protection Platform can query the external Identity store, then return the list of requested users or groups. If you want to display all user or group entries, enter the wildcard character (*).

      Press Shift+click to select multiple, contiguous users and groups. Press Ctrl+click to select multiple, discontiguous users and groups.

   4. In the Approvers field, select user or group Identities you want to assign to approve workflows (certificate approval or injection command) for the new application.

      The default approver is the master administrator. For more information on defining workflow objects, see Implementing certificate workflow management.

   5. (Conditional) If your application (or certificate) object is affected by a defined workflow and you want users to use a console other than Policy Tree, click Managed By and select which administration console to use as part of the workflow.

      You only need to configure this if you are using workflows and expect users to perform a task using a particular administration console. The default setting is Policy Tree.

      For more information, see Specify folders and certificates to be managed by TLS Protect .

6. Under Application Information, do the following:

   1. Click next to Application Credential to browse for the credential object that you want to use to authenticate with the application.

      DID YOU KNOW?  Credential objects store the credentials Trust Protection Platform uses to authenticate with devices, applications, and CAs. The stored credential might be a user name or private key credential; some drivers—such as F5, which is not SSH-based—can only use the user name credential for authentication.

      NOTE  The user account you select must have Read and Write access to the Temporary, Private Key, and Certificate directories.

      For more information, see Working with system 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.

   3. (Optional) In the Port field, type the port that Trust Protection Platform should use to communicate with the server where the application is installed.

      Trust Protection Platform uses the SSH protocol to communicate with the application server installed on Linux or Windows. The default SSH port assignment is port 22.

7. Under Adaptable Settings, do the following:

   1. (Read Only) If the PowerShell Script setting is blank, then you have not yet specified a script on this application object's parent policy.

      You can complete this procedure and then select the script in the policy later.

      For more information, see Assigning the PowerShell script to a policy.

   2. (Conditional)(Optional) If you did not select a private key credential on the parent policy already, or if you want to override the policy setting, click the Private Key Credential field and select one.

      Why do I need to select a private key credential? The private key credential is the password used to encrypt the private key in the encrypted form passed to the function (both PEM and PKCS#12). If not supplied, we'll generate a password internally for that purpose because it may only be needed to install the private key (i.e. the private is decrypted by the consumer when you import it). You can also set this on the policy level of that object.

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

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

   4. Complete the remaining fields, as defined by your PowerShell script.
8. When you're finished, click Save.