diff options
| author | Rich Megginson <rmeggins@redhat.com> | 2005-10-21 17:40:33 +0000 |
|---|---|---|
| committer | Rich Megginson <rmeggins@redhat.com> | 2005-10-21 17:40:33 +0000 |
| commit | 31b670a3185db254bc7767c63ce36aa213ba897b (patch) | |
| tree | 91ab519436314abed77137f4c79d497c6799b46b /ldap/synctools/passwordsync/passsync/syncserv.cpp | |
| parent | 860258059350b632b8600a546d3846cdc074e58a (diff) | |
Bug(s) fixed: 170350
Bug Description: RHDS to AD: entries with constraint violations not sync'ed
Reviewed by: Nathan and Noriko (Thanks!)
Branch: Directory71RtmBranch and HEAD
Fix Description: The DS correctly rejects the change and continues when
it gets a constraint violation from Windows AD in response to an
update. However, there is no way for the admin to know that this
occurred, and no easy way to find out what the problem is or how to fix
it. This fix just logs the error message from Windows at the default
log level, so an admin can know which entry and attribute had a
problem. Other log messages are logged at the repl log level, as
before. The other part of this is to remove the extraneous new line
chars from the Windows error message.
Platforms tested: RHEL4
Flag Day: no
Doc impact: Yes. We need to document a way for the user to fix the
problem and then re-sync the entry over to Windows. We also need a link
to detailed information about AD error messages.
QA impact: should be covered by regular nightly and manual testing
New Tests integrated into TET: none
Diffstat (limited to 'ldap/synctools/passwordsync/passsync/syncserv.cpp')
0 files changed, 0 insertions, 0 deletions
