Oracle Fusion Cloud Applications - Deactivate/Delete User

Oracle Fusion Cloud Applications - Deactivate/Delete User deactivates or deletes a user in Oracle Fusion Cloud Applications for:

Users 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:

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.

📘
Note:
To use this enforcement action, you must successfully configure a Oracle Fusion Cloud Applications adapter connection.

Deactivate or Delete - Select the action to perform.
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.

Host Name or IP Address - The hostname or IP address of the Oracle Fusion Cloud Applications server.
Client ID and Client Secret - The credentials for an account that has the Required Permissions to fetch assets.
Scope - The scope name.
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 following APIs:

Required Permissions

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

Authentication

Oracle supports Basic Auth (username + password) and Bearer token (OAuth2), depending on your tenant setup.

Roles & Entitlement

Every user calling SCIM REST endpoints must have the ASE_REST_SERVICE_ACCESS_IDENTITY_INTEGRATION_PRIV privilege.
Your user must be assigned the business task ‘Manage Users’ (or an equivalent custom role that includes the entitlement). For more information, see Use Cases.

For more details about other enforcement actions available, see Action Library.

Updated 4 days ago