Axonius Documentation
  1. Enforcement Action Library
  2. Manage Users and User Groups

IFS Assyst CMDB - Create Item

The IFS Assyst CMDB - Create Item Enforcement Action creates a new configuration item in IFS Assyst CMDB 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 Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - 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 IFS Assyst 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 IFS Assyst adapter connection.

  • Item Name - Name of the CMDB item to create.

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.

  • Short Code - Short code identifier for the item.
  • Serial Number - Serial number of the item.
  • Remarks - Description or remarks for the item.
  • Product Short Code - Short code of the associated product in IFS Assyst.
  • User Short Code - Short code of the assigned user in IFS Assyst.

  • Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way, you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

    📘

    Note:

    For details, see Axonius to External Field Mapping.

Connection Settings

💡

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 - Base domain for the IFS Assyst REST API (e.g., https://your-assyst-server.com).
  • User Name - Username for authentication with the IFS Assyst REST API.
  • Password - Password for authentication with the IFS Assyst REST API.
  • Product Class ID List - Optional comma-separated list of product class IDs to filter devices during adapter fetch operations.

  • Verify SSL (Optional) (default: enabled) - Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings. This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting.)

  • 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 IFS Assyst REST API v2 - POST /assystREST/v2/items

Required Ports

Axonius must be able to communicate via the following ports:

  • TCP port 80/443 (HTTP/HTTPS)

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

  • An IFS Assyst user account with permissions to create configuration items (CMDB items).

Note: The exact permission names should be confirmed with your IFS Assyst administrator or IFS support, as the publicly available API documentation does not include detailed permission information.

To learn more about Enforcement Actions, see Enforcement Actions.

Updated 1 day ago

Did this page help you?