Dashboard > Pulse v1.1 > ... > Settings > LDAP Configuration
  Pulse v1.1 Log In | Sign Up   View a printable version of the current page.  
  LDAP Configuration
Added by Jason Sankey, last edited by Jason Sankey on Aug 02, 2006  (view change)
Labels: 
(None)

Pulse Manual Index

Overview

Pulse is able to optionally authenticate users against an existing LDAP server. To authenticate against LDAP, provide the details required to connect to your LDAP server and an LDAP filter to identify users. You may then add users that are authenticated via LDAP rather than pulse passwords. Using the "auto add new users" option you can also allow new pulse users to be created for usernames authenticated successfully via LDAP.

Configuration

enable ldap integration

Check this box to enabled LDAP authentication for your pulse server.

ldap host url

The URL of your LDAP host, including the port to connect to.

This setting is required.

Example

ldap://ldap.example.com:389/

base dn

The base distinguished name under which to search for users.

This field is required.

Example

dc=example,dc=com

manager dn

Distinuished name for the manager account if required for initial binding. Required when your LDAP server does not allow anonymous binding.

Example

cn=admin,dc=example,dc=com

manager password

The password for the manager account, only used when a manager dn is provided.

user filter

An LDAP filter used to locate the user matching the login name provided by the user to pulse. This login name may be referred to in the filter by using the ${login} variable.

Examples

A typical, simple search:

(uid=${login})

Typical active directory search:

(sAMAccountName=${login})

A search restricted to users in the "developers" group:

(&(uid=${login})(group=developers))

auto add new users

If this box is checked, users that are successfully authenticated via LDAP can be automatically added to pulse. When a user provides a login that does not exist in pulse, authentication against LDAP will be attempted. If the authentication is successful, the user will be added to pulse automatically, to be authenticated via LDAP. Pulse will attempt to retrieve the user's full name from the LDAP server.

email attribute

If set, this value is used as the name of an attribute in the user records that contains the user's email address. When a user is added via the auto-add mechanism, the value of this attribute will be used to create an email contact point for the user.

If this value is not set no contact point will be created for auto added users.

Example

mail

Overview

Pulse is able to optionally authenticate users against an existing LDAP server. To authenticate against LDAP, provide the details required to connect to your LDAP server and an LDAP filter to identify users. You may then add users that are authenticated via LDAP rather than pulse passwords. Using the "auto add new users" option you can also allow new pulse users to be created for usernames authenticated successfully via LDAP.

Configuration

enable ldap integration

Check this box to enabled LDAP authentication for your pulse server.

ldap host url

The URL of your LDAP host, including the port to connect to.

This setting is required.

Example

ldap://ldap.example.com:389/

base dn

The base distinguished name under which to search for users.

This field is required.

Example

dc=example,dc=com

manager dn

Distinuished name for the manager account if required for initial binding. Required when your LDAP server does not allow anonymous binding.

Example

cn=admin,dc=example,dc=com

manager password

The password for the manager account, only used when a manager dn is provided.

user filter

An LDAP filter used to locate the user matching the login name provided by the user to pulse. This login name may be referred to in the filter by using the ${login} variable.

Examples

A typical, simple search:

(uid=${login})

Typical active directory search:

(sAMAccountName=${login})

A search restricted to users in the "developers" group:

(&(uid=${login})(group=developers))

auto add new users

If this box is checked, users that are successfully authenticated via LDAP can be automatically added to pulse. When a user provides a login that does not exist in pulse, authentication against LDAP will be attempted. If the authentication is successful, the user will be added to pulse automatically, to be authenticated via LDAP. Pulse will attempt to retrieve the user's full name from the LDAP server.

email attribute

If set, this value is used as the name of an attribute in the user records that contains the user's email address. When a user is added via the auto-add mechanism, the value of this attribute will be used to create an email contact point for the user.

If this value is not set no contact point will be created for auto added users.

Example

mail

Zutubi wiki is Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.10 Build:#528 Nov 29, 2006) - Bug/feature request - Contact Administrators