Bug 566124

Summary:	configure-proxy.sh should not change password for jabberd
Product:	[Community] Spacewalk	Reporter:	Miroslav Suchý <msuchy>
Component:	Proxy Server	Assignee:	Miroslav Suchý <msuchy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.8
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:	2010-05-05 14:57:07 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:
Bug Depends On:
Bug Blocks:	559281

Description Miroslav Suchý 2010-02-17 11:07:03 UTC

Description of problem:
When we run configure-proxy.sh we will install new c2s.xml and sm.xml. During this action we will overwrite username and pass for access to local database. We should handle it similary as spacewalk-setup-jabberd in spacewalk server.

Comment 1 Miroslav Suchý 2010-02-17 11:13:27 UTC

> The jabberd c2s configuration refused to allow SSL to start - had to
> copy the c2s.xml file from the spacewalk server over and then amend
> the component password and the realm to be correct for the proxy.
This will be the same problem as above. It should be fixed if we use the same c2s.xsl from spacewalk-jabberd-setup.

Comment 2 Miroslav Suchý 2010-02-24 16:11:01 UTC

Fixed in commit 2a53041fa4ce870cab91a732a9368b5cac49af89
Now we use spacewalk-setup-jabberd to directly modify jabberd configuration files and we do not distribute our own config files any more.

Comment 3 Miroslav Suchý 2010-05-05 14:57:07 UTC

This bug has been fixed in Spacewalk 1.0.
Closing.