Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 607547

Summary: ManagementAgent::init() has some poorly chosen defaults
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-qmfAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED UPSTREAM QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: beta   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:13:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gordon Sim 2010-06-24 10:53:34 UTC
Description of problem:

qpid::agent::ManagementAgent::init() defaults userid, password and mechanism to guest, guest and PLAIN respectively. Having these defaults encourages users to ignore the issue of authentication for their agents, leading to possible issues at deployment time.

Comment 1 Matthew Farrellee 2010-06-24 14:20:59 UTC
condor_triggerd is currently relying on defaults for MA::init()

Discussion led to conclusion that the defaults should not specify a specific mechanism, allowing SASL to pick from installed mechanisms.

Comment 2 Ted Ross 2010-06-29 17:57:55 UTC
I've removed the blocker flag and 1.3 target from this bug but I've left the bug open so we don't lose track of this issue.

The general issue is to decide what the correct default should be for SASL-mechanism.

If the default is "", SASL will pick from what's available.  This is good except that the behavior may vary based on which SASL packages are installed.

Comment 4 Red Hat Bugzilla 2025-02-10 03:13:30 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.