Okta - Enable Users enables each user by reactivating, or unsuspending the users retrieved from 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.
- Not all asset types 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.
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 Okta 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.
To use this option, you must successfully configure an Okta adapter connection.
- Action to perform on Okta Users - Select the action to perform on the Okta users, either to Unsuspend or Reactivate 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.
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.
- 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.
- 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 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.