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/10/29 17:07:59 UTC
[jira] Created: (QPID-2174) When kerberos auth is used, Java client
should use the kerberos userid & domain when setting the userid in messages
When kerberos auth is used, Java client should use the kerberos userid & domain when setting the userid in messages
-------------------------------------------------------------------------------------------------------------------
Key: QPID-2174
URL: https://issues.apache.org/jira/browse/QPID-2174
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.5
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.6
If kerberos auth is used, the java client should use the userid & domain when setting the user id in messages
Currently the java client just uses the user id specified in the connection.
--
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
[jira] Commented: (QPID-2174) When kerberos auth is used, Java
client should use the kerberos userid & domain when setting the userid in
messages
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771464#action_12771464 ]
Rajith Attapattu commented on QPID-2174:
----------------------------------------
The c++ broker currently strips the domain to accommodate the java client.
Once the java client is fixed the C++ broker should also be modified QPID-2175
> When kerberos auth is used, Java client should use the kerberos userid & domain when setting the userid in messages
> -------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2174
> URL: https://issues.apache.org/jira/browse/QPID-2174
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.6
>
>
> If kerberos auth is used, the java client should use the userid & domain when setting the user id in messages
> Currently the java client just uses the user id specified in the connection.
--
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
[jira] Resolved: (QPID-2174) When kerberos auth is used, Java
client should use the kerberos userid & domain when setting the userid in
messages
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-2174.
------------------------------------
Resolution: Fixed
I have checked in a fix at rev 898505 in Qpid trunk.
> When kerberos auth is used, Java client should use the kerberos userid & domain when setting the userid in messages
> -------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2174
> URL: https://issues.apache.org/jira/browse/QPID-2174
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
>
> If kerberos auth is used, the java client should use the userid & domain when setting the user id in messages
> Currently the java client just uses the user id specified in the connection.
--
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
[jira] Updated: (QPID-2174) When kerberos auth is used, Java client
should use the kerberos userid & domain when setting the userid in messages
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-2174:
-----------------------------------
Fix Version/s: (was: 0.6)
0.7
Moving items unlikely to be completed for 0.6 out to 0.7
> When kerberos auth is used, Java client should use the kerberos userid & domain when setting the userid in messages
> -------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2174
> URL: https://issues.apache.org/jira/browse/QPID-2174
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
>
> If kerberos auth is used, the java client should use the userid & domain when setting the user id in messages
> Currently the java client just uses the user id specified in the connection.
--
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