RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1278426 - Better error message needed for invalid ca-signing-algo option
Summary: Better error message needed for invalid ca-signing-algo option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Babinsky
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 13:02 UTC by Kaleem
Modified: 2016-11-04 05:39 UTC (History)
2 users (show)

Fixed In Version: ipa-4.4.0-0.el7.1.alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 05:39:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Kaleem 2015-11-05 13:02:00 UTC 
Description of problem:
I think there should be a better error message when invalid or empty option used with --ca-signinig-algorithm option.

[root@dhcp207-229 ~]# ipa-server-install --setup-dns --forwarder=10.65.201.89 -r TESTRELM.TEST -a xxxxxxxx -p xxxxxxxx --external-ca -U --ca-signing-algorithm=invalid
Usage: ipa-server-install [options]

ipa-server-install: error: option --ca-signing-algorithm: invalid choice 'invalid' (choose from s, e, t, (, [, ', S, H, A, 2, 5, 6, w, i, t, h, R, S, A, ', ,,  , ', S, H, A, 1, w, i, t, h, R, S, A, ', ,,  , ', S, H, A, 5, 1, 2, w, i, t, h, R, S, A, ', ], ))
[root@dhcp207-229 ~]# 

[root@dhcp207-229 ~]# ipa-server-install --setup-dns --forwarder=10.65.201.89 -r TESTRELM.TEST -a xxxxxxxx -p xxxxxxxx --external-ca -U --ca-signing-algorithm=
Usage: ipa-server-install [options]

ipa-server-install: error: option --ca-signing-algorithm: invalid choice '' (choose from s, e, t, (, [, ', S, H, A, 2, 5, 6, w, i, t, h, R, S, A, ', ,,  , ', S, H, A, 1, w, i, t, h, R, S, A, ', ,,  , ', S, H, A, 5, 1, 2, w, i, t, h, R, S, A, ', ], ))
[root@dhcp207-229 ~]# 

Version-Release number of selected component (if applicable):
[root@dhcp207-229 ~]# rpm -q ipa-server
ipa-server-4.2.0-15.el7.x86_64
[root@dhcp207-229 ~]# 

How reproducible:
Always

Steps to Reproduce:
1. ipa-server-install with invalid ca-signing-algo option.
2.
3.

Actual results:

Usage: ipa-server-install [options]

ipa-server-install: error: option --ca-signing-algorithm: invalid choice '' (choose from s, e, t, (, [, ', S, H, A, 2, 5, 6, w, i, t, h, R, S, A, ', ,,  , ', S, H, A, 1, w, i, t, h, R, S, A, ', ,,  , ', S, H, A, 5, 1, 2, w, i, t, h, R, S, A, ', ], ))


Expected results:
..
Usage: ipa-server-install [options]

ipa-server-install: error: option --ca-signing-algorithm: invalid choice 'invalid' (choose from SHA256withRSA, SHA1withRSA, SHA512withRSA)
Comment 2 Petr Vobornik 2015-11-05 13:25:20 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5433
Comment 3 Martin Bašti 2015-11-11 09:47:05 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/b6a2a1cfd2d811e4df77e5b90324d1453dab4b18
ipa-4-2:
https://fedorahosted.org/freeipa/changeset/dc0f2d1fec8bdbe5cccebb1d3dfe403ad994e6f6
Comment 4 Mike McCune 2016-03-28 23:02:11 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 6 Kaleem 2016-09-12 05:56:40 UTC 
Verified.

IPA Version:
============
[root@dhcp207-129 ~]# rpm -q ipa-server
ipa-server-4.4.0-10.el7.x86_64
[root@dhcp207-129 ~]# 

console output:
===============

[root@dhcp207-129 ~]# ipa-server-install --setup-dns --auto-forwarders --auto-reverse --hostname=dhcp207-129.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address=10.65.207.129 --ca-signing-algorithm=invalid -U
Usage: ipa-server-install [options]

ipa-server-install: error: option --ca-signing-algorithm: invalid choice 'invalid' (choose from 'SHA1withRSA', 'SHA256withRSA', 'SHA512withRSA')
[root@dhcp207-129 ~]# ipa-server-install --setup-dns --auto-forwarders --auto-reverse --hostname=dhcp207-129.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address=10.65.207.129 --ca-signing-algorithm= -U
Usage: ipa-server-install [options]

ipa-server-install: error: option --ca-signing-algorithm: invalid choice '' (choose from 'SHA1withRSA', 'SHA256withRSA', 'SHA512withRSA')
[root@dhcp207-129 ~]#
Comment 8 errata-xmlrpc 2016-11-04 05:39:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2404.html
Note You need to log in before you can comment on or make changes to this bug.