Bug 1012273 - rhncfg-manager should have option to specify server's CA cert
rhncfg-manager should have option to specify server's CA cert
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Client (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
Depends On:
Blocks: 462714
  Show dependency treegraph
Reported: 2013-09-26 03:23 EDT by Martin Korbel
Modified: 2018-04-09 06:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-09 06:50:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Korbel 2013-09-26 03:23:59 EDT
Description of problem:
We do not have way how to specify CA certificate on command line. You have to go to /etc/sysconfig/rhn/rhncfg-manager.conf to fix it. 

I think, it is good idea that we would able to specify CA certification on command line, if we can specify --server-name, --username and --password.

BTW: we have not chance to change https to http on command line.

Version-Release number of selected component (if applicable):
rhncfg-management-5.10.55-5.el6sat (sat5.6.0)

How reproducible:

Steps to Reproduce:

> export PASSWD='xxx'
> spacewalk-api --server localhost --user=admin --password=$PASSWD configchannel.create "%session%" "etc" "etc" "etc"
> echo "xxx" > reproducer_file
> chmod 0000 reproducer_file
> rhncfg-manager add --username=admin --password=$PASSWD --server-name=$(hostname) -c etc reproducer_file
Using server name <fqdn>
XML-RPC error while talking to https://<fqdn>/CONFIG-MANAGEMENT-TOOL: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]

Actual results:
I have not found a way how to do so.

Expected results:
There might be option like --ca-cert (satellite-sync have that)
Comment 2 Tomas Lestach 2018-04-09 06:50:10 EDT
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.

Note You need to log in before you can comment on or make changes to this bug.