- 18 Sep 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
Salesforce - Delete Extensions
- Updated on 18 Sep 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
Salesforce - Delete Extensions deletes extensions in Salesforce 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.
The EC knows which extensions to delete from the adapter name and Extension ID received from entity query.
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 Salesforce adapter - Select this option to use the first connected adapter credentials.
- Select Adapter Connection - Select which adapter connection to use for this Enforcement Action.
Required Fields
These fields must be configured to run the Enforcement Set.
Title (default: Axonius-created ticket) - Enter a title for the case. It is recommended to use a short description of the case as a title. The default title is "Axonius-created ticket".
Account ID - ID of the account associated with this case.
Contact ID - ID of the associated contact.
Description - Enter a description of the case.
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.
- Gateway Name - Select the Gateway through which to connect to perform the action.
Connection and Credentials
When Use stored credentials from the adapter is toggled off, these fields need to be configured:- Domain - The full URL of the Salesforce server.
- User Name and Password - The credentials for a user account that has the Required Permissions to fetch assets.
- User Secret - The Salesforce security token associated with a user account to fetch assets.
- Consumer Key - A consumer key associated with a user account that has the Required Permissions to fetch assets.
- Consumer Secret - A consumer secret associated with a consumer key.
- 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.
APIs
Axonius uses the Salesforce Developers API.
Required Permissions
The value supplied in User Name and Consumer Key must have permissions to manage users, as per Salesforce - Get User Information for Multiple Users.
Version Matrix
This Enforcement Action 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 |
---|---|---|
Salesforce 5.0 | Yes |
For more details about other Enforcement Actions available, see Action Library.