Link BMC FootPrints Ticket

Link BMC FootPrints Ticket links tickets in BMC Footprints 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 BMC Footprints 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 a BMC FootPrints adapter connection.

• first_ticket_id - The unique numerical identifier (Record ID) of the first ticket in the relationship.
• first_ticket_definition_id - The unique internal identifier (Record Definition ID) specifying the type of the first ticket.
• second_ticket_id - The unique numerical identifier (Record ID) of the second ticket in the relationship.
• second_ticket_definition_id - The unique internal identifier (Record Definition ID) specifying the type of the second ticket.
• link_type_name - The descriptive name of the relationship type that defines the connection between the two tickets.

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

Ticket Main Settings

These fields are optional.

• Submitter - The user who created and submitted the ticket into the FootPrints system.

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 hostname or IP address of the BMC FootPrints server.
• User Name and Password - The credentials for a user account that has the Required Permissions to fetch assets.

• 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 BMC FootPrints Service Core Web Services.

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 80/443

Required Permissions