The attribute ntUserFlags is not synchronized now in Active Directory replication agreements. This attribute is the equivalent of UserAccountControl in the Active Directory side, and their values are equivalent according to [1] and [2]. The only flag that could be problematic is PASSWD_CANT_CHANGE [3].
389-DS 1.2.5, CentOS 5.5 i386; Windows Server 2003 Standard Edition, Service Pack 2, 32 bits
[0] Original mailing list post: http://markmail.org/thread/tvhnn7t2dped4hfk
[1] http://www.mail-archive.com/mozilla-directory@mozilla.org/msg00638.html [2] How to use the UserAccountControl flags to manipulate user account properties: http://support.microsoft.com/kb/305144/en-us [3] Modifying User Cannot Change Password (LDAP Provider): http://msdn.microsoft.com/en-us/library/aa746398.aspx
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @nkinder: - Issue assigned to rmeggins - Issue set to the milestone: FUTURE
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/339
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.