This code duplicates the basic function of lastbind. The two overlays
cannot be used together. The timestamp Mod op is changed to require
the old value to still be present at the end of the Bind. This allows
us to detect collisions (multiple successful Binds in the same time
window) and properly fail the extra Bind attempts.

Only drop connection if user originally bound to this backend,
and rebind-as-user was set. Sessions from other backends would
use idassert-bind so loss of creds doesn't affect them.

Ryan Tandy authored 9 years ago and Howard Chu committed 9 years ago

The fix for ITS#7016 only adjusted the frontend entry's DN, but not the
naming attribute in the entry. check_name_index knows how to do both.

also cleanup of return-code handling

Test less likely condition first

Change result of MDB_IDL_ALL() to use the last entryID in the DB
instead of NOID.

slap_auxprop_lookup() returns void with old sasl versions.

Don't change mc_dbx because we would need to undo the change if
the txn aborts. Make the fix (for get) match existing code for put.

This reverts commit 47c4e747.

Revert "ITS#8117 fix INTEGERDUP compare"

This reverts commit ba45e0c0.

Thomas Cort authored 9 years ago and Howard Chu committed 9 years ago

The LDIF output wasn't being explicitly flushed. In certain scenarios,
such as piping the output of a persistent ldapsearch to node.js v0.12
on Mac OS X 10.10.3, the output is unavailable to the process
consuming the search results until the stdio buffer fills (8192 bytes
for example). This can leave the tail end of persistent search results
in the buffer for a long time (until enough output has accumulated).

Explicitly call flush so that the output is immediately available.