Choosing login values 

Determine which LDAP attribute or attributes you to use to log in to IBM Connections.

The following scenarios are supported:

Single LDAP attribute with a single value

Multiple LDAP attributes, each with a single value

Single LDAP attribute with multiple values

Multiple LDAP attributes, each with multiple values

Multiple LDAP directories


Multi-valued attributes

You can map multiple values to common attributes such as uid or mail.

If, for example, you mapped the following attributes for a user called Sample User, all three values for the user are populated in the PROFILE_LOGIN table in the Profiles database:

A similar example for the uid property would have the following attributes:

By default, the population wizard only allows you to choose one attribute for logins, so you can't select mail and uid. You can, however, write a custom function to union multiple attributes.


Custom attributes

The Profiles population wizard populates uid and mail during the population process but maps the loginID attribute to null. You can specify a custom attribute if your directory uses a unique login attribute other than, for example, uid, mail, or cn. The login value can be based on any attribute that you have defined in your repository. You can specify that attribute by setting loginID=attribute when you populate the Profiles database.

The following sample extract from the profiles-config.xml file shows the standard login attributes:

<loginAttributes> 
<loginAttribute>uid</loginAttribute> 
<loginAttribute>email</loginAttribute> 
<loginAttribute>loginId</loginAttribute> 
</loginAttributes> 

The value for the loginID attribute is stored in the Prof_Login column of the Employee table in the Profiles database. For more information, see the Mapping fields manually topic.


Using Profiles or LDAP as the repository

The default login attributes that are defined in the profiles-config.xml file are uid, email, or loginID

If you change the default IBM Connections configuration to use the LDAP directory as the user repository, WAS maps uid as the login default.


Parent topic

Preparing to configure the LDAP directory

Related concepts
Specify the global ID attribute for users and groups


Related tasks


Specify a custom ID attribute for users or groups
Setting up federated repositories
Mapping fields manually


   

 

});

+

Search Tips   |   Advanced Search