...
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 this option it is possible to control the visitors Sitecore user's membership information, role, and profile role, user profile, landing page and more, directly from Salesforce. The most common way to implement roles is called "Multi-role" where fields in the Salesforce contact (or lead) record 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).
...
The Security Connector for Contacts is only required if you want visitors to log into the Sitecore website using credentials stored in a Salesforce contact record. The Security Connector overrides the ASP.NET membership provider so user data is stored in Salesforce but appears in Sitecore under the “salesforce” domain name. After installing this option it is possible to control the visitors Sitecore role, user profile, landing page and more, directly from Salesforce.
Installation
IMPORTANT: The connector has a number of install options and some may not be necessary for your requirements. |
...