Directory Integration Overview
Using the Lightweight Directory Access Protocol (LDAP), you can sync the users in the Socialcast community with your company’s central user database. In this process, also known as directory integration, LDAP imports information from the master database to create Socialcast user accounts for all community members and then updates the user information in Socialcast whenever the corresponding information changes in the master database. If your company maintains multiple user databases, you can instruct Socialcast to mirror all of them.
Note: LDAP is not available for Socialcast Free accounts; it is only available for paid communities.
How It Works
Socialcast provides an LDAP script, written in Ruby, that reads a configuration file for information about the location of your LDAP databases and the fields you want to map. Using the instructions in the configuration file, the script extracts information from the LDAP databases, creates a compressed XML file, and then uploads the file to the Socialcast server. Socialcast then updates its user profile information with the data in the XML file.
What You Need
To use the LDAP feature, you must have the enterprise version of Socialcast; the free version does not support LDAP. This feature works with any type of Socialcast deployment: SaaS, private cloud, or behind the firewall (On-Premise). If you have an On-Premise installation, however, we recommend you set up LDAP using the Socialcast Cluster Management Console
Because the LDAP script is Ruby-based, you’ll need to install Ruby and RubyGems on a physical or virtual machine behind your firewall which can access your LDAP databases. You do not need to know how to use Ruby, but you should be familiar with your LDAP installation and have access to a Socialcast community administrator account.
Here’s a quick overview of the LDAP set-up process:
||First you need to install Ruby and RubyGems on your system.
||Install and configure the Socialcast gem.
||Next you install the Socialcast gem and generate a default configuration file.
||Customize the default configuration file.
||In the configuration file you must specify connection information for the LDAP databases, define which LDAP fields map to the Socialcast user profile fields, and define the behavior of the script during the import process.
||Test the script.
||Then you can test the script and examine the resulting XML file to ensure that it contains the desired data.
||Prevent users from updating the LDAP fields.
||Before you roll out the functionality in the community, you should modify the Socialcast user profile page so that users can’t update the fields that LDAP populates.
||Run the script.
||Finally, you can run the script to create Socialcast accounts for the target users in your LDAP databases and then schedule the script to run on a regular basis.
Read Setting Up LDAP
for detailed information about the set-up process.