ds.git/ldap/servers/plugins, branch Directory71RtmBranchPoint

Bug(s) fixed: 158549

2005-05-24T01:14:48+00:00

Bug Description: Reliab 05: chaining backend test core dumped on HPUX backend
Reviewed by: Noriko (Thanks!)
Fix Description: This is a 64 bit issue.  For ber_scanf, the "i" and "e" flags require a pointer to a long.  There were a couple of places in the chaining backend code where we were passing in an int instead.  This works fine on 32 bit where ints and longs are both 32 bits.  I did a quick check through the code - these were the only places not using longs.  The only way you would see this bug is in a "hub" chaining backend - one that gets requests from a mux and chains them to another farm server, or possibly on a mux in certain conditions.
Platforms tested: HP-UX 11.i 64 bit
Flag Day: no
Doc impact: no
QA impact: rerun chaining tests
New Tests integrated into TET: none

Fix for #158253: add attributes to the exclusion list for fractional replication. Add an error string returned to clients if an illegal attribute is configured

2005-05-20T03:57:34+00:00

Only check the read only status of the consumer for the fractional case if the acquire process has been successful thus far.

2005-05-18T03:17:33+00:00

Correctly report in the repl agreement status attrs that the repl init failed when it failed due to attempting to do fractional replication to another master.

2005-05-18T02:17:21+00:00

Fix for 157919: perform fractional consumer check after acquiring the replica

2005-05-17T18:40:08+00:00

Fix for #157901 : FMR in windows sync agreement code

2005-05-16T22:26:25+00:00

Change NT4 case to send plaintext passwords

2005-05-12T03:46:20+00:00

Bug(s) fixed: 157377

2005-05-11T18:51:54+00:00

Bug Description: RL16: Server core dumped while configuring replication agreements
Reviewed by: David (Thanks!)
Fix Description: The code for handling bad agreements was wrong.  It was not returning the correct error code.  The result of this is that the client did not receive an appropriate error code/message from the server.  The reason for the core dump was that, even though the agreement was not created, the DSE entry was still there, causing the server to become very confused.  Returning the correct error code causes the server to refuse to create the bad DSE entry.
Platforms tested: RHEL3
Flag Day: no
Doc impact: no
QA impact: should be covered by regular nightly and manual testing
New Tests integrated into TET: none

Fix for #156449 : mangle 'street' attribute to defeat our schema aliasing it with 'streetaddress'

2005-05-09T20:34:31+00:00

Fix for 157021: server doesn't correctly process modifies to windows sync agreements

2005-05-06T03:35:52+00:00