Unregistration is a hack and we shoould either make the subsystems into
an entry (if monitor allows subentry generation) or implement subsystem
unregistration in back-monitor.

An operation is rejected iff it has to be dropped before we can find an
upstream for it (unless we handle it ourselves, that is). At that point
it is failed unless completed successfully.

This makes a difference for multi-stage binds which alternate between
'failed' (we are waiting on a server response) and 'completed' (server
did what we asked them to, waiting on client to continue).

Trying to abandon an operation does not automatically make it completed,
it might have failed already but we're just racing to reach the client
to record that.

During response processing, an upstream connection could be marked ready
after a different bind had already been allocated to it, thus allowing
two binds to be in progress on the same connection.

Takes care of dealing with monitor not present/not configured and fix a
monitor startup issue.

Ondřej Kuzník authored Jan 16, 2018 and Ondřej Kuzník committed Nov 17, 2020

For a new bind request, this is obvious, for SASL bind requests, we do
not know the final identity until we have finished handling it, make
sure it stays empty until then.

Ondřej Kuzník authored Dec 13, 2017 and Ondřej Kuzník committed Nov 17, 2020

Will only try to extract the TLS client certificate name if used during
the last handshake.