Install Security Connector for Contacts (Optional)


You can use create, view, edit, or delete Salesforce records by creating functionality inside Sitecore portal pages. The portal page is only accessible after visitors login to the website using a login control. Installing the Security Connector for Contacts option allows privileged customers, employees, partners, or any other entity, represented in Salesforce as Contacts, to login to your Sitecore website using credentials stored in their Contact record.

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 this option it is possible to control the visitors Sitecore 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). 

  IMPORTANT: The Security Connector is only required if you are using a custom login control. A typical use would be allowing privileged customers, or internal staff, to access Sitecore portal pages.

  IMPORTANT: The Security Connector requires a login control on your website.

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. 


IMPORTANT: The connector has a number of install options and some may not be necessary for your requirements.

These wiki pages cover the installation steps needed to install and configure the optional FuseIT S4S Security Connector. 

The FuseIT S4S Security Provider is distributed as a Sitecore Package and also requires a package to be installed into Salesforce. 

Modifications of Configuration Files

It is assumed that the modifications to the configuration files have already been made for authenticating against a Salesforce Contact.

Next Step (Optional)

Install Security Connector in Salesforce for Contacts