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.
> 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.
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.
This bug has been fixed in Spacewalk 1.0. Closing.