[QPID-8219] [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 authentication providers per connection basis

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: qpid-java-6.1.6, qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-broker-7.0.0, qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6
• Fix Version/s: qpid-java-6.1.7, qpid-java-broker-7.1.0, qpid-java-broker-7.0.7
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 17/Jul/18 10:03
• Updated: 03/Sep/18 00:13
• Resolved: 27/Aug/18 16:49

Description

SimpleLdap and OAUTH2 authentication providers were supposed to cache authentication results per remote host basis. Thus, when connections are made from the same host using the same credentials, the cached authentication result should be reused. The current caching approach takes into consideration an ephemeral port of the connection. As result, a new connection from the same host with the same credentials cannot reuse previous authentication result due to a different ephemeral port.