-
Right now the implementation of EXTERNAL authentication mechanism is highly tuned towards using https and certificates for authentication which isn't truly "external" - in theory we should define an interface that takes the connectTo, User, Password and the LDAP connection, and returns either void or the LDAP connection (perhaps they want to set up an entirely new connection).
2007-08-10 19:37:30 UTC in OpenLDAP ILM Management Agent
-
adamjw committed revision 68 to the OpenLDAP ILM Management Agent SVN repository, changing 1 files.
2007-08-09 00:48:51 UTC in OpenLDAP ILM Management Agent
-
adamjw committed revision 67 to the OpenLDAP ILM Management Agent SVN repository, changing 1 files.
2007-08-08 21:02:33 UTC in OpenLDAP ILM Management Agent
-
If there is still work to do here (int and string watermark comparisons) let's leave this bug open (or else close this one and open a new one for those).
2007-07-09 23:54:00 UTC in OpenLDAP ILM Management Agent
-
Was this fixed? Which revision? Please comment and close.
2007-07-09 23:52:11 UTC in OpenLDAP ILM Management Agent
-
Was this fixed? Which revision? Please comment and close.
2007-07-09 23:50:09 UTC in OpenLDAP ILM Management Agent
-
Was this fixed? Which revision? Please comment and close.
2007-07-09 23:48:31 UTC in OpenLDAP ILM Management Agent
-
Was this fixed? Which revision? Please comment and close.
2007-07-09 23:47:51 UTC in OpenLDAP ILM Management Agent
-
I think we should check affirmatively for success here - based on my reading of the docs the LdapException is only thrown "The System.DirectoryServices.Protocols.LdapException class is an exception that occurs when LDAP returns an error code not included in System.DirectoryServices.Protocols.ResultCode." - However it looks like there are result codes where no Entries are returned but my guess is...
2007-07-09 23:46:48 UTC in OpenLDAP ILM Management Agent
-
One thing I was thinking was moving the ChangePassword and SetPassword methods back into the passwordextension.cs file to keep the "Utils" class clean and focus on only including re-usable routines in Utils.
We could make the connection a public Property of the Utils class (keep direct field access to the member variable private) and have InitConnection return a reference to Connection object.
2007-07-09 23:35:27 UTC in OpenLDAP ILM Management Agent
