For this modification, I'm not using any controls. The attributes are not null either. We set the cn and sn (which are required) to the string 'null' when the entry is created to have a stub entry. Then we update, replace modification those fields, add modification on new fields with the user provided data. The password policy control I use only on a bind request to see if they are expiring, need to change pw, etc. I'll try M18 and get back to you in about 30 minutes.
-----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Tuesday, June 25, 2013 3:38 AM To: [email protected] Subject: Re: M13 and api M17 Le 6/25/13 12:59 AM, [email protected] a écrit : > Hi, I'm using the M13 build and Api M17. > I create an entry no problem then try and update it with a Modification[] > array and it fails. > I've tried it with and without the userPassword and the same issue occurs. > Without digging in too deep, is there anything you can see from the message? > We just swapped out M11 server for M13 ( startup with new partitions) and > tried to create a new user. > Do we need to use the M18 API with this release? Will work to provide more > information. Thanks! > More specifically, I wonder if you are using the PasswordPolicy control. I would be interested to know if using M18 imrpovs the result you get. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
