Bug 772959

Summary: "qpidd.sasldb" lost after qpid-0.12 upgrade to qpid-0.14
Product: Red Hat Enterprise MRG Reporter: Petra Svobodová <psvobodo>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: DevelopmentCC: iboverma, jneedle, jross, lzhaldyb, matt, sgraf, timp
Target Milestone: 2.1.2   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 20:17:09 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 Petra Svobodová 2012-01-10 14:07:10 UTC
Description of problem:
After upgrade qpid-0.12 to qpid-0.14 the original database file "qpidd.sasldb" was deleted and no new database file added. That is why authentication on the broker fails. 
This behaviour is different from previous versions and it is inconsistent with the Messaging Installation Guide (http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html/Messaging_Installation_Guide/chap-Messaging_Installation_Guide-Authentication_and_Authorization.html)   

Version-Release number of selected component (if applicable):
[root@hostname]# rpm -qa | grep qpid
qpid-qmf-0.14-2.el5
qpid-cpp-server-cluster-0.14-3.el5
qpid-qmf-devel-0.14-2.el5
qpid-qmf-debuginfo-0.10-6.el5
python-qpid-qmf-0.14-2.el5
qpid-java-client-0.14-1.el5
qpid-cpp-client-0.14-3.el5
python-qpid-0.14-1.el5
qpid-cpp-server-ssl-0.14-3.el5
qpid-cpp-server-store-0.14-3.el5
qpid-cpp-server-devel-0.14-3.el5
qpid-cpp-client-ssl-0.14-3.el5
qpid-java-common-0.14-1.el5
qpid-cpp-server-xml-0.14-3.el5
qpid-cpp-client-devel-docs-0.14-3.el5
qpid-cpp-mrg-debuginfo-0.10-6.el5
qpid-cpp-client-devel-0.14-3.el5
qpid-tools-0.14-1.el5
qpid-cpp-server-0.14-3.el5
qpid-java-example-0.14-1.el5

How reproducible:
100%

Steps to Reproduce:
1. Currently install qpid-0.12 messages and make sure if the "qpidd.sasldb" is located in its default location (/var/lib/qpidd/qpidd/sasldb)
2. Upgrade qpid-0.12 to qpid-0.14 using "yum" command. 
3. Look at the /var/lib/qpidd/ directory and try to authenticate to broker using predefined account "guest" with password "guest"
  
Actual results:
"qpid.sasldb" file is not in its default location as is described in documentation 

Expected results:
"qpid.sasldb" should be in its default location or documentation should be actualized according to the current state