ServiceNow - Assign Role to User
  • 23 Sep 2024
  • 3 Minutes to read
  • Dark
    Light
  • PDF

ServiceNow - Assign Role to User

  • Dark
    Light
  • PDF

Article summary

ServiceNow - Assign Role to User assigns role(s) to each user returned by the saved query supplied as a trigger (or users selected in the asset table).

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

Note:

General Settings

  • 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 ServiceNow adapter - Select this option to use Workspace adapter credentials.
    • When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
Note:

To use this option, you must successfully configure a ServiceNow adapter connection.

Required Fields

  • Role IDs (comma separated) - Enter a comma separated list of role IDs. Users will be added to or removed from these roles, depending on your selection in the dropdown below.
  • Add/Remove assignment - 'Add' is selected by default.
  • 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.

  • ServiceNow Domain - The hostname or IP address of the ServiceNow server. This field format is 'https://[instance].service-now.com'.

  • User Name and Password - The credentials for a user account that has the Required Permissions to add users.

  • Client ID and Client Secret - The OAuth Client ID and Client Secret for OAuth access to ServiceNow. Refer to OAuth 2.0 with Inbound REST for full details on how to obtain the OAuth Token.

  • Refresh Token - When using the OAuth method of authentication, enter the value of the Refresh Token issued by a ServiceNow instance.

  • 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.

  • Fetch devices updated in ServiceNow in the last X hours (0: All) (default: 0) - Enter an amount of hours to fetch only devices that have been updated in ServiceNow in the last specified number of hours.

  • Fetch users updated in ServiceNow in the last X hours (0: All) (default: 0) - Enter an amount of hours to fetch only users that have been updated in ServiceNow in the last specified number of hours.

  • Fetch users created in ServiceNow in the last X hours (0: All) (default: 0) - Enter an amount of hours to fetch only users that have been created in ServiceNow in the last specified number of hours.

  • Advanced configuration file - Upload an advanced configuration JSON file.

  • Enable Client Side Certificate - Select to enable Axonius to send requests using the certificates uploaded to allow Mutual TLS configuration for this adapter. When you select this option, 2 more fields are displayed:

  • Client Certificate File (.pem) - Adds a client side certificate to the connection.

    • Click Choose file next to Client Certificate File to upload a public key file in PEM format
  • Client Private Key File (.pem) - Adds a private key to the connection (if the API/proxy requires identification).

    • Click Choose file next to Client Private Key File to upload a client private key file in PEM format
  • Gateway Name - Select the Gateway through which to connect to perform the action.

Required Permissions

The credentials used to connect to ServiceNow must have permission to assign roles to users.


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



Was this article helpful?