...
IMPORTANT: The Security Connector is only required if you are using a custom login control.
not required that requires a package to be installed in Salesforce. This install lets visitors The Security Connector is optional. It is only required if you want visitors to log into the Sitecore website using credentials stored in a Salesforce Contact or Lead record. It requires a package to be installed in Salesforce.
The Security Connector overrides the ASP.NET membership provider so user data is only stored in Salesforce but appears in Sitecore in the “Salesforce” domain. This is commonly called "a single source of truth". After installing the Security Connector it is possible to control the Sitecore user membership information, roles, and profiles from Salesforce. Note there are two ways to implement roles - choose only one:
- Single role using the Salesforce Account to specify the Sitecore role. All contacts that belong to the Account will be Sitecore users in a Sitecore role with the same name as the Salesforce Account.
- Multi-role using fields in the contact (or lead) record to specify the Sitecore role. One or more Sitecore roles have the same names as selections in a custom multi-pick list in the Salesforce contact (or lead). Multi-role is more flexible than single role.
- Single role using the Salesforce Account to specify the Sitecore role. All contacts that belong to the Account will be Sitecore users in a Sitecore role with the same name as the Salesforce Account.
Campaign Members as Sitecore Roles
...