LDAP Configuration
From AgileApps Support Wiki
Revision as of 00:28, 21 November 2013 by imported>Aeric (→Configuration Settings)
> 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.
Considerations and Limitations
- 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.
How LDAP Works
User Experience
Effect on Platform Operations
Configuring LDAP
- 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]
Configuration Settings
- 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 -
- The &category=person and object(Class=User) parameters do not need to be specified. They are included automatically.
- Group DN -
- Group DN Filter -
- The Group search:
- The &group= parameter does not need to be specified. It is included automatically.
- Default Team -
- Default Access Profile -
- LDAP Attribute for Access Profile -
- Note: The field must contain the role's record ID, not the name of the role.
- Default Application -
- LDAP Attribute for Application -
- 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: