You should review the information about creating users and cloning community profiles in Salesforce Communities. For more information, see the Salesforce Communities integrations documentation.

  1. Go to Integrations > Provisioning.
  2. Click + and then click New connection.
  3. On the Identity Store line, click Select.
  4. Click Salesforce Communities, click Select, and then click Next.
  5. Enter a name and description for this provisioning connection. The connection name will appear in the list when you've completed and saved the connection.

    The connection name appears in provisioning the list after you save the connection.

  6. Click Next.
  7. On the Configure authentication screen, enter the following:
    Field Value

    Salesforce domain

    The full domain for the Salesforce account.

    Tip:

    You can find the domain in the URL when lsigned on to the account. For example, <myCompanyName>.my.salesforce.com.

    Client ID

    The Consumer Key value from Salesforce for the connected application.

    For more information, see Create a Connected App in the Salesforce documentation.

    Client secret

    The Consumer Secret value from Salesforce for the connected application.

    OAuth access token

    The access token from Salesforce for the connected application.

    Tip:

    You can use the Ping Identity OAuth Configuration Service (OCS) to get the token. For more information, see Getting an API access token from Salesforce.

    OAuth refresh token

    The refresh token from Salesforce for the connected application.

  8. Click Test connection to verify that PingOne can establish a connection to Salesforce Communities.

    If there are any issues with the connection, a Test Connection Failed dialog box opens. Click Continue to resume the setup with an invalid connection.

    You cannot use the connection for provisioning until you have established a valid connection to Salesforce. Click Cancel to modify the settings and try again.

  9. On the Configure preferences screen, enter the following:
    Option Description

    Permission set management

    Determines how to handle permission sets in the Salesforce Communities identity store.

    Select Merge with permission sets in Salesforce or Overwrite permission sets in Salesforce. If you select Merge with permission sets in Salesforce and a permission set is added in the data store, PingOne adds it to the user's existing permission sets in Salesforce Communities.

    PingOne does not remove any permission sets added in Salesforce Communities by other sources. If you select Overwrite permission sets in Salesforce and a permission set is added or removed in the data store, PingOne overwrites the user's permission sets in Salesforce Communities with those from the data store.

    Allow users to be created

    Determines whether to create a user in the Salesforce Communities identity store when the user is created in the PingOne identity store.

    Allow users to be updated

    Determines whether to update user attributes in the Salesforce identity store when the user is updated in the PingOne identity store.

    Note:

    If you clear the Allow users to be updated or Allow users to be disabled check boxes, the child options that depend on a user update will become unavailable.

    Allow users to be disabled

    Determines whether to disable a user in the Salesforce Communities identity store when the user is disabled in the PingOne identity store.

    Action when disabling users

    Determines the action to take when deprovisioning users from the Salesforce Communities identity store:

    • Disable. When deprovisioning, PingOne disables the user. The user cannot sign on, and their data is not visible to other users in Salesforce Communities.
    • Freeze. When deprovisioning, PingOne freezes a user. The frozen user cannot sign on, but the user's data, such as profile and activity, is still visible to other users in Salesforce Communities.

      For more information, see Freeze or Unfreeze User Accounts in the Salesforce documentation.

    Allow users to be deprovisioned

    Determines whether to deprovision a user in the Salesforce Communities identity store when the user is deprovisioned in the PingOne identity store.

    Remove action

    Determines the action to take when removing a user from the Salesforce Communities dentity store.

    Deprovision on rule deletion

    Determines whether to deprovision users if the associated provisioning rule is deleted.

  10. Click Finish.

The Salesforce Communities provisioning connection is complete and is added to the list of provisioning connections on the Provisioning page.

To sync group members out of PingOne into a Software as a Service (SaaS) application, follow the instructions in Configuring outbound group provisioning.