Contents x
    Admin By Request - Approve or Deny Ticket
    • 20 Oct 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Admin By Request - Approve or Deny Ticket

    • Updated on 20 Oct 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Admin By Request - Approve or Deny Ticket approves or denies ticket requests (created by Admin by Request) for:

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

    See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

    Note:

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
    • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

    • Use stored credentials from the Admin by Request 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 Admin by Request adapter connection.
    • Ticket Action - The possible values are Approve or Deny.

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

    Additional Fields

    These fields are optional.

    • Host Name of IP Address (required) - The hostname or IP address of the Admin by Request server.
    • API Key (required) - An API Key associated with a user account that has permissions to fetch assets. Refer to Obtaining the API Key for more details.
    • 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 User Name (optional) - The user name to use when connecting to the server using the  HTTPS Proxy.
    • HTTPS Proxy Password (optional) - The password 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 Admin By Request Inventory API.

    Required Permissions

    The stored credentials, or those provided in Connection and Credentials, must have Edit or Write permissions to perform this Enforcement Action.

    Version Matrix

    This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

    VersionSupportedNotes
    6.1Yes

    For more details about other Enforcement Actions available, see Action Library.


    Was this article helpful?
    What's Next