I'm in the process of trying to adapt Turbine to use LDAP rather than SQL to
store
user information. As part of this process, I need to use LDAP
authentication to
confirm username and password; this process involves presenting the password
to the
LDAP server, rather than retrieving the password and comparing it on the
client side.
Unfortunately, the current user authentication scheme puts the
validateUser(user, pwd) method in UserFactory, and builds in the assumption
that the password is retrieved and
compared. If this were replaced with a User.validate() method taking no
arguments,
derived, specialized user classes could handle their own validation in any
desired way
without requiring changes to the Turbine base code. This would seem to be a
better
compartmentalization of design.
Any comments? If this makes sense, is anyone with more experience than I
interested
in taking it on, or should I give it a shot myself? (I have essentially
zero open-
source dev experience, so I'm a bit wary about trying to do this.)
--
Craig Berry - (310) 570-4140
Senior Software Engineer
GlueCode
1452 Second St
Santa Monica CA 90401
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
