Ektron 9.00
Lightweight Directory Access Protocol (LDAPLightweight Directory Access Protocol; permits access to distributed information.) is a set of protocols that enable the hierarchical arrangement of corporate directory entries in a structure, which may reflect geographic or organizational boundaries. Active Directory and LDAP are not the same. While they perform similar functions, LDAP (when used with Ektron) only verifies login information and creates the user in the Everyone group.
Ektron's LDAP feature lets you retrieve user login information from an LDAP server. As a result, you can administer user information from one place, and users only need to remember one password/username combination to sign on to the network and Ektron.
The hierarchical structure of LDAP authentication can be organized in several different ways. For example, if you had the following LDAP structure, the domain would typically span multiple countries.
NOTE: Abbreviations: CN = Common Name, OU = Organizational Unit, O = Organization, C= Country, DN = Distinguished Name.
CN=j_smith, OU=Sales, O=MyCompany, C=US, DN=example.com
By changing the order of C and DN, the hierarchy indicates that the domain example.com
is located in the US.
CN=j_smith, OU=Sales, O=MyCompany, DN=example.com, C=US.
In some instances, it may be necessary to have an Organization appear below an Organizational Unit. For example, your Organizational Unit has it own Organizations.
Below is a visual example of an LDAP hierarchical structure.
You enable LDAPLightweight Directory Access Protocol; permits access to distributed information. by editing the web.config
file and editing settings on the Active Directory Setup screen. See Also: Setting Up Active Directory
IMPORTANT: Before enabling LDAP in Ektron, make sure your LDAP server is ready for use. Be sure to include an Ektron administrator account for yourself. After you enable LDAP, only the BuiltIn account can access Ektron without LDAP authentication. See Also: Getting Started with Ektron
siteroot\web.config
file, change the ek_AUTH_Protocol
property to GC:<add key="ek_AUTH_Protocol" value="GC"/>
When adding Organizational Units, paths are comma-separated and run from specific to general. For example, ou=Amherst,ou=New Hampshire,o=US.
For more information, see Adding an Organizational Unit During Setup.
Do not add individual Common Names here. Only add Organizational Units that contain people who should have access to Ektron. To add a single individual from a different Organizational Unit, see Adding User Information from an LDAP Server to Ektron
NOTE: You can add additional Organizations below an Organization Units as long as the path on your LDAP server is the same.
\web.config
file, add the Username and Password for ek_ADUsername
and ek_ADPassword
. For example:<add key="ek_ADUsername" value="mwright@ektron.com" />
<add key="ek_ADPassword" value="mypasswordisthis" />
Things to consider when adding Organizational Units:
ou=Sales
, ou=Sales_Service
, and ou=MyCompany
, which lets you authenticate users listed in Sales, Sales_Sevice, and MyCompany.Users at each level are automatically available for adding to Ektron. You do not have to be at the OU or CN level to add a user. If a user is at the DC or OU level, they are available.
After LDAPLightweight Directory Access Protocol; permits access to distributed information. is enabled, there are several ways to add LDAP user information to Ektron:
Prerequisite
LDAP is enabled. See Enabling LDAP.
To search for a user on an LDAPLightweight Directory Access Protocol; permits access to distributed information. server and add the user to Ektron:
Prerequisite
LDAP is enabled. See Enabling LDAP.
The Browse LDAP feature provides a friendly and intuitive way to find usernames, domains/organizations and organizational units.
IMPORTANT: The default server IP/DNS name and port are taken from the settings specified in the Configuration > Setup page. These settings must be specified before connecting to the LDAPLightweight Directory Access Protocol; permits access to distributed information. server.
Before using the browse feature, you must specify an Organizational Unit that can see the user in the Configuration > Setup page.
Prerequisite
LDAP is enabled. See Enabling LDAP.
NOTE: In the LDAP Explorer, the Path and Org/Domain fields update dynamically as you navigate through the LDAP tree.
It is important to note that Ektron does not write to the LDAPLightweight Directory Access Protocol; permits access to distributed information. server. So, while you can change fields when editing a user in Ektron, you also need to make the same changes on the LDAP server.
If a user is deleted on the LDAPLightweight Directory Access Protocol; permits access to distributed information. server, Ektron does not automatically delete the user. However, the user’s login fails because the login cannot be authenticated. In this case, delete the user from Ektron using the Delete User function.
NOTE: If you mistakenly delete all users with administrative privileges, you can still sign in using the builtin user’s username and password. See Also: Getting Started with Ektron
Usually Membership users are not included in AD or LDAP directories. Ektron's default settings ignore AD or LDAPLightweight Directory Access Protocol; permits access to distributed information. for membership authentication.
If you want Membership users to authenticate with AD or LDAP, follow these steps.
web.config
file.LDAPmembershipUser
to true.<add key "ek_LDAPMembershipUser" value="true" />
ek_LDAPmembershipUser
is false, membership users are not authenticated with AD or LDAP.To disable LDAP authentication or integration, edit the Active Directory Setup screen and select Disable Active Directory and LDAP Authentication.
See Also: Setting Up Active Directory