Bug 742786 - Need to pass sasl-mech-list value for Wallaby broker connection
Summary: Need to pass sasl-mech-list value for Wallaby broker connection
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: cumin
Version: Development
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 2.1
: ---
Assignee: Trevor McKay
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-02 20:07 UTC by Trevor McKay
Modified: 2011-10-03 19:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-03 19:02:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Trevor McKay 2011-10-02 20:07:20 UTC 
Description of problem:

  The sasl-mech-list parameter restricts the mechanisms that are allowed for connection to the messaging broker for condor and sesame objects.

  The Wallaby integration into cumin uses a separate session with its own broker connection.  The connection to the broker for wallaby needs to use a sasl-mech-list parameter for the same reasons.  Currently it is not.

Additional info:

Problems can arise when cumin connects to a broker with credentials for PLAIN authentication but the broker has ANONYMOUS authentication enabled as well and authenticates the connection as ANONYMOUS.  The sasl-mech-list allows cumin to restrict the mechanisms it will accept.
Comment 1 Trevor McKay 2011-10-03 13:18:47 UTC 
Fixed in revision 5034.

The connection to the broker for wallaby data will use the same sasl-mech-list setting as other broker connections.
Comment 3 Trevor McKay 2011-10-03 19:02:05 UTC 
Fixed in 5037.
Note You need to log in before you can comment on or make changes to this bug.