Julien Vehent <[email protected]> writes: > On Tue, 14 Sep 2010 10:51:01 +0200, Emmanuel Lecharny <[email protected]> > wrote: >> On 9/14/10 8:40 AM, mailing lists wrote: >>> Hello, >>> >>> I think that the pwdAttribute needs an OID value (specified by the syntax) >>> so you would must use the OID of the userPassword attribute which is >>> 2.5.4.35 >>> >>> >>> >>> >>> >> I thought that would be a possibility for the failure Kiran and Julien are >> facing, (please guys, can you give it a try ?), but IMO, there is no reason >> why we would not be allowed to use 'userPassword' in this context. >> Using the OID instead of the alias name does not carry any extra >> information, as soon as the alias is valid accordingly to the schema >> (whatever it represents, be it an AT, OC, MR, or any of the other >> kind of schema objects). The syntax should just check that the alias >> is syntaxically correct. It's up to the ppolicy overlay to check >> that the value is a valid AT. >> Plus the error message is really misleading if this is the cause for >> the error. > > > I tried with the OID... same thing. > How can I check that the module is properly loaded and functional ?
ldapsearch -x -H ldap://some.host -b "" -s base supportedControl\ | grep '1.3.6.1.4.1.42.2.27.8.5.1' -Dieter -- Dieter Klünter | Systemberatung sip: [email protected] http://www.dpunkt.de/buecher/2104.html GPG Key ID:8EF7B6C6
