Action1 - Deploy Package

Action1 - Deploy Package triggers Action1 to deploy packages for:

• Assets returned by the selected query or assets selected on the relevant asset page.

Required Fields

These fields must be configured to run the Enforcement Action.

• Use stored credentials from the Action1 adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

  • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

    📘

    Note

    To use this option, you must successfully configure an Action1 adapter connection.

• Automation Name - The custom name you gave to the specific Automation (policy) that triggered this deployment.
• Template ID - The unique internal identifier (GUID/UUID) for that specific software definition in the Action1 library.
• Template Name - The human-readable name of the software or script as it appears in the Action1 Software Repository.
• Action Display Name - The readable name of the specific action item within the execution queue. It is often very similar to the Automation Name but refers specifically to the execution instance visible in the "Actions" or "History" tab.
• Package ID - The unique identifier for the specific build of the software being deployed.
• Package Version - The actual version number of the software being installed.
• Organization ID - The unique identifier for your company or tenant within Action1.

• Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

These fields are optional.

💡

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

• Host Name or IP Address - The host name or the IP address of the Action1 server.
• Client ID and Client Secret - The credentials for a user account that has the Required Permissions to perform this Enforcement Action.

• Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

• HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

• HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

• HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

• Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the Action1 API.

Required Permissions