Difference between revisions of "LDAP Configuration"

Revision as of 00:25, 21 November 2013

> Administration > Account Management > LDAP Configuration

If the enterprise has an LDAP server, the platform can be configured to automatically recognize selected users when they log in.

Active Directory is currently supported. Open LDAP is under development.
A single LDAP server is supported, currently.
The search for a matching user .
It cannot span multiple ___s, as yet--so a CN entry must be included either in the search DN or the filter.
The user's Team cannot currently be configured using LDAP attributes.
The default team is always used.

Examine the configuration settings below to see which user attributes can be populated from LDAP.
Create attributes for those settings in your LDAP server.
Go to > Administration > Account Management > LDAP Configuration
Fill in the configuration settings
Click [Save]

Server Type - Active Directory (default)
Server URL - The server domain and optional portal. Secure portal #636 is the default. Ex: LDAP:998
Login DN -
Password -
Starting Search Directory -
User DN -
User DN Filter -
Group DN -
Group DN Filter -
Default Team -

Note: The field must contain the role's record ID, not the name of the role.

Note: The field must contain the role's record ID, not the name of the role.

Default Role -
LDAP Attribute for Role - The name of an LDAP field that designates the user's role in the default application.

Note: The field must contain the role's record ID, not the name of the role.

Tip: To get record IDs, use the following procedure:

Navigate to the object in question (Access Profiles, Applications, or Roles)
> Objects > {object}
Edit the default view or create a new view for your use.
Modify the view to include the Record ID field.
View the entries in that object
Take the record ID from the column you added to the view.

@@ Line 6: / Line 6: @@
 :* Active Directory is currently supported. Open LDAP is under development.
 :* A single LDAP server is supported, currently.
+:* The search for a matching user .<br>It cannot span multiple ___s, as yet--so a <tt>CN</tt> entry must be included either in the search DN or the filter.
 :* The user's Team cannot currently be configured using LDAP attributes.<br>The default team is always used.
-:*
 ==How LDAP Works==