AgileApps Support Wiki Pre Release

Difference between revisions of "LDAP Configuration"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 3: Line 3:
If the enterprise has an {{^LDAP}} server, the platform can be configured to automatically recognize selected users when they log in.
If the enterprise has an {{^LDAP}} server, the platform can be configured to automatically recognize selected users when they log in.
__TOC__
__TOC__
===Considerations and Limitations===
==Considerations and Limitations==
:* Active Directory is currently supported. Open LDAP is under development.
:* Active Directory is currently supported. Open LDAP is under development.
:*  
:* A single LDAP server is supported, currently.
:* The user's Team cannot currently be configured using LDAP attributes.<br>The default team is always used.
:* The user's Team cannot currently be configured using LDAP attributes.<br>The default team is always used.
:*
:*


===How LDAP Works===
==How LDAP Works==
===User Experience===
===Effect on Platform Operations===


===LDAP Configuration Settings===
==LDAP Configuration Settings==
:* '''Server Type -'''  
:* '''Server Type -'''  
:* '''Server URL -'''  
:* '''Server URL -'''  

Revision as of 00:13, 21 November 2013

GearIcon.png > 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 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

LDAP Configuration Settings

  • Server Type -
  • Server URL -
  • Login DN -
  • Password -
  • Starting Search Directory -
  • User DN -
  • User DN Filter -
  • Group DN -
  • Group DN Filter -
  • 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.

Thumbsup.gif

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

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