Hi, It's been a while, been travelling around Mexico & Guatemala recently and was unable to post this to the group before I left. Anyway hope this makes a few folk happy.
Problem: Ldap code in Turbine is broken. It's unclear (for me) what we actually want to achieve with Ldap; authentication only, replace DataBase with ldap server combination Ldap/DB. Solution: As a first step and to get a discussion going I've adapted the code to at least get Authentication working. The solution is built largely on the code that was already available from the Gluecode people with some changes from me. I don't see this code as final and welcome feedback/ideas/integration advice etc. to achieve what we want. The major change is the addition of a helper class (LdapFunctions) which encapsulates the code required for communication with the server. Further changes were made to the LdapUserManager to use this new class. The manner in which it works is that a User logs in with say uname + passwd. A search is made on the server useing a known DistinguishedName + password. If a user is found, the DistinguishedName + passwd from THAT user is used to bind to the server, if successful the user is authenticated. Room for improvement could be the pooling of the first connection(s) but is not yet implemented. What I'm looking at now and would welcome advice on before posting the code (if required) is the User/TurbineUser/LDAPUser objects. The present (DataBase) situation works with a TurbineUser object which gives (Casting) problems (understandably) when Authentication takes place against an Ldap server where an LDAPuser object is used. /Colin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
