Box - Delete User
Box - Delete User deletes Box Platform users 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:
- 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.
-
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.
- Box Platform private key configuration file - The private key configuration file that provides the Required Permissions to fetch assets.
- Force Delete - Forces the deletion of the user regardless of other requirements.
- Notify User - Send the user an email to notify them of their deletion from Box.
-
Gateway Name - Select the Gateway through which to connect to perform the action.
APIs
Axonius uses the following BOX APIs:
- Delete user - API Reference - Box Developer Documentation
- Upload file - for file size up to 20MB.
- Create upload session - for file size over 20MB.
Required Permissions
The value supplied in Box Platform private key configuration file refers to the generated private key configuration file for your Custom App using JWT authentication:
-
Set up a Custom App - Set up a Custom App using JWT authentication. For details, see Box Guides - Setup with JWT.
-
Create Box Platform private key configuration file - After a Custom App has been created to use JWT authentication, there is an option available in the Developer Console to have Box create a configuration file. This file will include the keypair as well as a number of other application details that are used during authentication.
- Click on the "Configuration" option from the left sidebar in your application and scroll down to the "Add and Manage Public Keys" section.
(728).png)
- Click the "Generate a Public/Private Keypair" button to have Box generate a keypair. This will trigger the download of a JSON configuration file that you can move to your application code.
- Upload this file as the Box Platform private key configuration file.
-
Application Scopes - The configured app must have the following application scopes:
- Read all files and folders stored in Box
- Read and write all files and folders stored in Box
Updated about 1 hour ago