[toc]
Telligent Community supports the use of LDAP for syncing Role and Profile information between your community and Active Directory.
Prerequisites
- Telligent Community license installed, with the "Telligent Enterprise" entitlement
- Your web and job servers must be domain joined to the domain you're
Install the LDAP Package
All steps must be followed before LDAP will work on your community.
-
Open the Packages.config file in both community's web directory, and Job Server (by default).
Out of the box, you should have the following in your packages.config file. However, if you do not see this section, add it verbatim:
<?xml version="1.0" encoding="utf-8"?>
<!-- This file determines which packages have been added to Telligent Community -->
<Packages>
<Package Name="Evolution" Version="1.0" DateInstalled="2009-03-09" Id="12994783-22B4-47fe-822A-B71B6F1B6C83" />
</Packages>The package is required and should not be removed.
-
To configure LDAP authentication, you will need to add (not substitute) the following line between the “<Packages>” tags in the XML:
<Package Name="Ldap" Version="1.0" DateInstalled="2009-03-09" Id="4BF1091D-376C-42b2-B375-E2FE9480E845" />
This file is case-sensitive, so if you use "name" instead of "Name" then you will have issues with your configuration. Also, the "Id" must be a unique number across all of the package entries.
Configuring LDAP Connection Details
-
Update the LDAP.config file with your the mappings of Telligent to AD profile fields . Click here to learn more about the LDAP.config file.
-
Supply your LDAP connection details to Telligent Community by doing the following:
-
Open both the web.config file in your web directory, and Telligent.Jobs.Server.exe.config in your Job Server directory.
- Locate the line that says <configSections>. In this top section, add the following line:
<section name="LdapConnection" type="System.Configuration.NameValueSectionHandler" />This section does not go in any of the existing section groups. Place the line right before the closing tag of <configSections>as in the following example:<configSections>
<section name="LdapConnection" type="System.Configuration.NameValueSectionHandler" />
</configSections> -
Add the section below right after the closing tag of </configSections> (so that it's between </configSections> and <appSettings>).
<LdapConnection> <add key="Server" value="LDAP://" /> <add key="Port" value="389" /> <add key="Authentication" value="Secure" /> </LdapConnection>
The attributes of an LDAP connection provide the following elements:
Attribute Name Attribute Description Server The address where the LDAP server can be found. If configured with "LDAP:\\" or "GC:\\", then the directory servers are auto detected based on teh current machine's Active Directory domain memberhsip. Port The port number where the LDAP server is listening for requests. BaseDN The base Distinguished Name. UserDN
The Distinguished Name for the user that will be used by Community Server to connect to the LDAP server. If not specified, will connect as your Application Pool Identity. Password
The password that will be used by Community Server to connect to the LDAP server. If not specified, will connect as your Application Pool Identity. Authentication
The authentication type that will be used on the connection. Default is Secure. A value of Secure will result in NTLM authentication being used. A value of SecureSocketsLayer will result in an SSL- encrypted authentication being used. More values can be found in the "Members" table here. -
Save the web.config file.
-
-
You should now be able to sync LDAP roles to Telligent Community, as well the profile fields configured in ldap.config
If running in a Multi Domain environment, see Configure Telligent Community in a multi-domain environment