Summary: Missing information about cyrus-sasl-plain package Description of problem: Messaging Installation Guide and Management Console Installation Guide assumes that cyrus-sasl-plain package is installed on RHEL server. It was true with RHEL5, because it installs 'Base' group, but not the case in RHEL6 with 'Minimal install' [1]. There are however installed other necessary packages [2]: cyrus-sasl cyrus-sasl-lib Therefore user will configure Messaging [3] and Management [4] with provided binaries in documentation: /usr/sbin/saslpasswd2, /usr/sbin/sasldblistusers2 and they are part of cyrus-sasl-lib so configuration will go smoothly. The only problem will be, that it won't work with SASL Plain Authentication that is described in documentation examples and is needed for correct cumin operation. When this happens, user get after login to cumin message: --- This console is not connected to any brokers and as a result has no management data to display. To connect, set the brokers configuration parameter in the [common] section of the config file located at /etc/cumin/cumin.conf. or ~/.cumin.conf [common] brokers: broker1.server.com,broker2.server.com Without a user-specified setting, cumin looks for a broker at localhost:5672. If you wish to use this configuration, make sure there is a broker with QMF enabled running at this address. --- And in qpidd log we can see: qpidd[1572]: 2011-10-05 16:37:39 warning Client closed connection with 501: Desired mechanism(s) not valid: PLAIN (supported: ANONYMOUS) (qpid/client/ConnectionHandler.cpp:250) --- As you can see below, the only way how to get this package to the system is: 1) Install group Base (not in Minimal installation) 2) Install any package requires needs cyrus-sasl-plain 3) Manually wisely install cyrus-sasl-plain [root@rhel6 temp]# yum groupinfo * | grep -e Group: -e cyrus-sasl-plain | grep -B 1 cyrus-sasl-plain Group: Base cyrus-sasl-plain [root@rhel6 temp]# repoquery --whatrequires cyrus-sasl-plain cyrus-sasl-plain-0:2.1.23-8.el6.i686 cyrus-sasl-plain-0:2.1.23-8.el6.i686 libpurple-0:2.7.9-3.el6.i686 Proposed action (prioritized): 1) add cyrus-sasl-plain as dependency to cumin package 2) describe in documentation that cyrus-sasl-plain has to be installed Version-Release number of selected component (if applicable): RHEL 6.1 How reproducible: 100% Steps to Reproduce: 1. Install RHEL6.1 with 'Minimal' option [1] 2. Install and configure cumin + qpid 3. Login to cumin and go to overview page Actual results: cyrus-sasl-plain isn't mentioned in documentation and in one of MRG packages dependency Expected results: cyrus-sasl-plain should be rpm dependency of cumin (or documented accordingly) Additional info: [1] http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-pkgselection-x86.html [2] Bug 593309 [3] http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html/Messaging_Installation_Guide/chap-Messaging_Installation_Guide-Authentication_and_Authorization.html [4] http://docs.redhat.com/docs/en-US/Red_Ha
If we are going to provide deployment instructions, they should be with cyrus-sasl-md5 (DIGEST-MD5) instead of PLAIN. Doing so is currently blocked by bug 749600.
Also note, adding a dependency for cumin on cyrus-sasl-plain/md5 won't work because cumin is not required to run on the same machine as the broker. This will have to be a documentation step.
Possible duplicate: Bug 758151 - chapter 7: No information of cyrus-sasl packages requirement for particular authentication methods
Yes, I think this is now a duplicate since 758151 has been created and instructions for enabling PLAIN have been included in the Messaging docs. The MCIG refers to the Messaging books with a notice, that should be sufficient. Note, when 752381 is resolved and we address 749600 in some fashion so that digest-md5 is available as an option, the MCIG will change to direct users toward digest-md5 instead. (In reply to comment #3) > Possible duplicate: > Bug 758151 - chapter 7: No information of cyrus-sasl packages requirement for > particular authentication methods
All referenced BZs were resolved. Closing as duplicate of Bug 758151 *** This bug has been marked as a duplicate of bug 758151 ***