What is LDAP support, concretely? What does it mean that
BugTracker.NET supports LDAP? A first step - my first step - is to
check users' passwords against the ones stored in the LDAP directory
instead of the ones stored in the database, so that passwords can be
the same across applications. The next step would be automatic user
creation. That is, for BugTracker.NET to work - for just about any
tracker to work - there needs to be a row in the tracker's database for
that user. It's not enough that the user exists in the LDAP
directory, it also needs to exist in the database. So, what a tracker
can do, if a user/password combo is authenticated against LDAP, is
create the database row the first time the user logs into the tracker.
The tracker could either create a bare bones user, with default
characteristics, or the tracker could use some attributes from LDAP to
set the corresponding attributes in the tracker db. For example, there
could be an attribute in the LDAP directory that BugTracker.NET should
intrepet as corresonding to the corresponding BugTracker.NET
"organization" of a user. Another way of using LDAP is to create a tool
that allows admins to do an initial mass import of users.
================
Sports Nutrition |
Sports Supplements