[jira] Created: (QPID-2647) Typo in str8-latin type definition for 0-10

Typo in str8-latin type definition for 0-10 --- Key: QPID-2647 URL: https://issues.apache.org/jira/browse/QPID-2647 Project: Qpid Issue Type: Bug Components: AMQP Compliance

[jira] Updated: (QPID-2647) Typo in str8-latin type definition for 0-10

[ https://issues.apache.org/jira/browse/QPID-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kennedy updated QPID-2647: - Attachment: 0001-QPID-2647-Fix-typo-in-str8-latin.patch Typo in str8-latin type definition for

[jira] Created: (QPID-2648) Connection close in 0-10 does not include 403 error code

Connection close in 0-10 does not include 403 error code Key: QPID-2648 URL: https://issues.apache.org/jira/browse/QPID-2648 Project: Qpid Issue Type: Bug Components: AMQP

[jira] Updated: (QPID-2648) Connection close in 0-10 does not include 403 error code

[ https://issues.apache.org/jira/browse/QPID-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kennedy updated QPID-2648: - Attachment: 0001-QPID-2648-Added-403-error-code-for-connection-close.patch Connection close in

[jira] Commented: (QPID-2648) Connection close in 0-10 does not include 403 error code

[ https://issues.apache.org/jira/browse/QPID-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12876191#action_12876191 ] Robbie Gemmell commented on QPID-2648: -- Checking the 0-10 spec, 403 isnt listed as a

Connection close codes question

All, I raised QPID-2648 to try and add the 403 (Unauthorized Access) exception code as a way of indicating why a 0-10 connection might be closed due to a security ACL failure, since the only codes available to me were: 200 / NORMAL 320 / CONNECTION_FORCED 402 / INVALID_PATH 501 / FRAMING_ERROR

Re: Qpid/Java Security Model

On 7 June 2010 06:49, Danushka Menikkumbura danus...@wso2.com wrote: Hi devs, AFAIK Qpid does not posses a pluggable security architecture. I basically need to integrate a custom security implementation - apart from the SASL/ACL based model that is there - so that I can use the security model

Re: Connection close codes question

On 06/07/2010 11:16 AM, Andrew Kennedy wrote: All, I raised QPID-2648 to try and add the 403 (Unauthorized Access) exception code as a way of indicating why a 0-10 connection might be closed due to a security ACL failure, since the only codes available to me were: 200 / NORMAL 320 /

Re: Qpid/Java Security Model

If you just want to use a custom source for username/password authentication data you can easily do that now by using the PrincipalDatabase interface used by the existing PlainPasswordFilePrincipalDatabase and Base64MD5PasswordFilePrincipalDatabase implementations, and then using the configuration

Re: Qpid/Java Security Model

Sounds good Robbie!. I will take a look and get back to you in case I hit any wall. Thanks, Danushka On Mon, Jun 7, 2010 at 5:11 PM, Robbie Gemmell robbie.gemm...@gmail.comwrote: If you just want to use a custom source for username/password authentication data you can easily do that now by

[jira] Updated: (QPID-2645) Qpid bugs found by static code analysis

[ https://issues.apache.org/jira/browse/QPID-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated QPID-2645: -- Attachment: RetractClient.patch qpid/cpp/src/qpid/cluster/RetractClient.cpp A destructor that consists

[jira] Created: (QPID-2649) Segfault on shutting down qpidd

Segfault on shutting down qpidd --- Key: QPID-2649 URL: https://issues.apache.org/jira/browse/QPID-2649 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Gordon Sim

[jira] Resolved: (QPID-2649) Segfault on shutting down qpidd

[ https://issues.apache.org/jira/browse/QPID-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2649. -- Resolution: Fixed Segfault on shutting down qpidd ---

[jira] Assigned: (QPID-2634) CRLF line endings in the shell scripts

[ https://issues.apache.org/jira/browse/QPID-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2634: Assignee: Robbie Gemmell CRLF line endings in the shell scripts

[jira] Updated: (QPID-2634) CRLF line endings in the shell scripts

[ https://issues.apache.org/jira/browse/QPID-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2634: - Status: Ready To Review (was: In Progress) CRLF line endings in the shell scripts

[jira] Resolved: (QPID-2634) CRLF line endings in the shell scripts

[ https://issues.apache.org/jira/browse/QPID-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-2634. -- Resolution: Fixed Patch applied, and appropriate line endings enforced in the repo on the major

[jira] Updated: (QPID-2589) Add a .NET binding to QPID Messaging API

[ https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated QPID-2589: -- Attachment: cpp_bindings_qpid_dotnet__cleanup.patch Cleanup pass to address function naming,

[jira] Resolved: (QPID-2600) ACL policy doesn't permit certain characters in usernames added to groups

[ https://issues.apache.org/jira/browse/QPID-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-2600. Resolution: Fixed The c++ acl module now allows all characters as specified in the acl

[jira] Commented: (QPID-2639) Add functionality to exclude any test using the current exclude mechanism

[ https://issues.apache.org/jira/browse/QPID-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12876440#action_12876440 ] Rajith Attapattu commented on QPID-2639: How about if we move QpidTestCase to the