Bug 1012273 - rhncfg-manager should have option to specify server's CA cert
rhncfg-manager should have option to specify server's CA cert
Status: NEW
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Client (Show other bugs)
560
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: 2015-10-09 04:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
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:
100%

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)

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