You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2009/12/18 05:00:18 UTC
[jira] Resolved: (QPID-2175) C++ broker should use userid@domain
when authenticating messages.
[ https://issues.apache.org/jira/browse/QPID-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-2175.
------------------------------------
Resolution: Fixed
A fix for this was added at rev 819819 in Qpid trunk.
However this caused QPID-2290 as the JMS Client does not have the concept of a domain name for a userID.
I added a proper fix for this where the broker now users default realm as the domain if the userID supplied in the message doesn't contain a domain.
This is added at rev 892123 in Qpid trunk.
> C++ broker should use userid@domain when authenticating messages.
> -----------------------------------------------------------------
>
> Key: QPID-2175
> URL: https://issues.apache.org/jira/browse/QPID-2175
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
>
> The c++ broker currently strips the domain from the user id when authenticating messages.
> This is to accommodate the java client issue defined in QPID-2174
> Once that is fixed the c++ broker should take the domain into account when authenticating messages.
> If a message contains a user id without a domain, the broker should use the realm as the default domain.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org