You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/08/07 11:16:00 UTC
[jira] [Commented] (QPID-8219) [Broker-J] Authentication results
are cached in SimpleLdap and OAUTH2 authentication providers per connection
basis
[ https://issues.apache.org/jira/browse/QPID-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571467#comment-16571467 ]
ASF subversion and git services commented on QPID-8219:
-------------------------------------------------------
Commit 603be3e7c523d1e796bad0281ca503ddafd21a93 in qpid-broker-j's branch refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=603be3e ]
QPID-8219: [Broker-J] Cache authentication results for the same remote hosts and credentials
(cherry picked from commit 4e240ba1a9bcdea65002c37101fd1889e16c6955)
# Conflicts:
# broker-core/src/test/java/org/apache/qpid/server/security/auth/manager/AuthenticationResultCacherTest.java
> [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 authentication providers per connection basis
> -------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8219
> URL: https://issues.apache.org/jira/browse/QPID-8219
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: 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
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0, qpid-java-broker-7.0.7
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org