Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-8219

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

    XMLWordPrintableJSON

    Details

    • 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
    • Component/s: Broker-J
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              orudyy Alex Rudyy
              Reporter:
              orudyy Alex Rudyy
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: