Contents x
    Salesforce - Assign Role or Profile to User
    • 10 Oct 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Salesforce - Assign Role or Profile to User

    • Updated on 10 Oct 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Salesforce - Assign Role or Profile to User assigns a role or profile to Salesforce user accounts 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:

    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 Salesforce 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.
      Note:
      To use this option, you must successfully configure a Salesforce.
    • Role Type (default: UserRole) - Select the role type to assign.
    • Role ID - Enter the ID of the role to assign.

    • 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.

    • Domain - The full URL of the Salesforce server.
    • Consumer Key - A consumer key associated with a user account that has the Required Permissions to perform this action.
    • Consumer Secret - A consumer secret associated with a consumer key.
    • Authentication Flow - Select the authentication flow to use.
    • 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.
    • 2FA Secret Key - The secret generated in Salesforce for setting up 2-factor authentication for the Salesforce user created for collecting SaaS Management data.
    • SSO Username and SSO Password - If your organization accesses Salesforce with an SSO provider (such as Google, Microsoft 365, Okta, etc.) enter your credentials for the SSO platform in the SSO Username and SSO Password fields.
    • Use Unified Login Domain - Select this option to use the http://login.salesforce.com URL for logging in instead of sub-domain.salesforce.com (if the main domain is a sandbox, the URL will be test.salesforce.com). This allows you to directly login with Salesforce credentials instead of using an external SSO.
    • 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.
    • Justification reason - Enter the justification for this action.

    APIs

    Axonius uses the Salesforce REST API.

    Required Permissions

    For more details about other Enforcement Actions available, see Action Library.

    Was this article helpful?
    What's Next