[DIRAPI-314] StartTLS operation is not correctly handled

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 2.0.0.AM3
• Assignee: Unassigned
• Reporter: Emmanuel Lécharny
• Created: 01/Apr/18 12:29
• Updated: 12/May/19 05:49
• Resolved: 03/Apr/18 17:01

Description

Currently, the startTLS operation waits for the ExtendedRespose to be received to add the SslFilter into the network chain. So far, so good, as it's not accepting any other operation while doing that (well, it does accept some new request, but they will be queued).
The problem arise when the response has been received, and once the SslFilter has been added : the SSL handshake starts, but as it's not blocking, it does not forbid other operations to be executed, and as the secured session may not yet established, those extra messages are going to be mixed with the handshake messages, leading to a closure of the connection.

We must find a way to wait for the handshake to be completed before allowing other operations to be accepted.