Okta - Disable Users

Updated on 28 Jan 2024
2 Minutes to read

Print
Share
Dark
Light
PDF

Article Summary

Share feedback

Thanks for sharing your feedback!

Okta - Disable Users can suspend, deactivate or delete each user retrieved from the saved query supplied as a trigger (or users selected in the asset table).

Note

To use this action, you must have Okta users in your Axonius environment.

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

General Settings

Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
  - See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
  - See Actions supported for Vulnerabilities.
  - See Actions supported for Software.
Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
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 Okta Adapter - Select this option to use the first connected Okta adapter credentials.

Note:

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

Required Fields

These fields must be configured to run the Enforcement Set.

Action to perform on Okta Users - Select the action to perform on the Okta users, either to suspend, deactivate or delete the users.
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.

Okta URL - The hostname or IP address of the Okta server. This field format is '[instance].okta.com'.
Okta API Key - An API key, created in the admin panel. For details, see Creating an API Token in Okta.
Number of parallel requests (default: 75) - Specify the maximum parallel requests that will be created when connecting to the value supplied in Okta URL.
API rate limit threshold percentage (default: 10) - Specify the threshold percentage of the Okta API rate limit when connecting to the value supplied in Okta URL. Axonius will stop the data fetch when the API rate limit reaches the supplied value.
HTTPS Proxy - A proxy to use when connecting to the value supplied in Okta URL.

Note:

If Use stored credentials from the Okta adapter is not enabled, the fields above are required.

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

APIs

Axonius uses the Core Okta API.

Permissions

The value supplied in Okta API Key must have write or admin permissions

Required Ports

Axonius must be able to communicate with the value supplied in Connection Settings via the following ports:

TCP port 443
TCP port 80

Version Matrix

This adapter has only been tested 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.

Version	Supported	Notes
Okta 4.5	Yes

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

Was this article helpful?

What's Next

Okta - Create Group

Table of contents

General Settings
Required Fields
Additional Fields
APIs
Permissions
Required Ports
Version Matrix