Bug 742786

Summary:	Need to pass sasl-mech-list value for Wallaby broker connection
Product:	Red Hat Enterprise MRG	Reporter:	Trevor McKay <tmckay>
Component:	cumin	Assignee:	Trevor McKay <tmckay>
Status:	CLOSED NEXTRELEASE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Development	CC:	jross, matt
Target Milestone:	2.1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-03 19:02:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.