Keeper - Delete User
- 20 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Keeper - Delete User
- Updated on 20 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Keeper - Delete User deletes users from Keeper Password Manager for:
- Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.
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 - 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 Keeper adapter - Select this option to use connected 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 Kandji adapter connection.
Required Fields
These fields must be configured to run the Enforcement Set.
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, these fields need to be configured:- Host Name or IP Address (default: keepersecurity.com) - The host name or the IP address of the Kandji server.
- User Name and Password - The user name and password of the account accessing the Keeper server.
- 2FA Secret Key - The two-factor authentication secret key received from Keeper.
- 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.
- Gateway Name - Select the Gateway through which to connect to perform the action.
APIs
Axonius uses the Keeper Secrets Manager SDK.
Required Permissions
The user account accessing Keeper Password Manager must have permissions to delete users.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?