Hi Nadya: Please let me know according to which document you should receive INSUFFICIENT_ACCESS_RIGHTS.
Regards, Obaid Farooqi Sr. Support Escalation Engineer | Microsoft From: Obaid Farooqi Sent: Thursday, July 01, 2010 10:22 AM To: 'nivan...@samba.org' Cc: cifs-proto...@samba.org; MSSolve Case Email Subject: RE:[REG:210063056197932001] Need some clarification on the User-Change-Password access rights Hi Nadya: My name is Obaid Farooqi and I'll be helping you with this issue. I'll be in touch as soon as I have anything concrete. Please feel free to contact me if you have a question/clarification. Regards, Obaid Farooqi Sr. Support Escalation Engineer | Microsoft From: didr...@gmail.com [mailto:didr...@gmail.com] On Behalf Of Nadezhda Ivanova Sent: Wednesday, June 30, 2010 6:31 AM To: Interoperability Documentation Help; cifs-proto...@samba.org Subject: Need some clarification on the User-Change-Password access rights Hello, I am currently working on enforcing the User-Change-Password control access right on password change operations in Samba 4, and there are a few things that puzzle me, perhaps you could help. I am testing agains a Win2008 server, domain and forest functional levels are 2008. The user object class has the following ACE in the defaultSecurityDescriptor: (OA;;CR;ab721a53-1e2f-11d0-9819-00aa0040529b;;WD), OA;;CR;ab721a53-1e2f-11d0-9819-00aa0040529b;;PS) I created a user and removed these two for the purposes of negative testing. However, when I performed a password change operation(delete and add of unicodePwd), I got CONSTRAINT_VIOLATION error rather than INSUFFICIENT_ACCESS_RIGHTS. I granted the user write property access, but the result was the same. Alternatively, a user to whom I explicitly denied WP access was able to change their password if they have User-Change-Password. So my question is: Is the write access to unicodePwd controlled only by User-Change-Password, and WP is disregarded in this case? Why is the error returned CONSTRAINT_VIOLATION? Also, given that by default we this control access right is granted to EVERYONE, this means that the actual line of defence is the changer knowing the original password. If they know the password, it does not matter which account changes the user's password, which makes sense. However, in this case, why bother with checking User-Change-Password at all? It appears that its purpose is to allow a user (or any account for that matter) to change the password even if they do not have WP access on themselves, am I correct? Best Regards, Nadya ________________________________ Microsoft is committed to protecting your privacy. Please read the Microsoft Privacy Statement<http://go.microsoft.com/fwlink/?LinkId=81184> for more information. The above is an email for a support case from Microsoft Corp. REPLY ALL TO THIS MESSAGE or INCLUDE casem...@microsoft.com<mailto:casem...@microsoft.com> IN YOUR REPLY if you want your response added to the case automatically. For technical assistance, please include the Support Engineer on the TO: line. Thank you.(*634135945473241748*)
_______________________________________________ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
