Red Hat Bugzilla – Bug 1140553
hammer --help redundantly requires credentials
Last modified: 2017-02-23 15:58:29 EST
Description of problem: Running hammer --help or e.g. hammer user --help (or any other command with --help) asks for foreman credentials. This is ridiculous, please remove it. Version-Release number of selected component (if applicable): rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch rubygem-hammer_cli_import-0.10.4-1.1.el6sat.noarch rubygem-hammer_cli-0.1.1-12.el6sat.noarch rubygem-hammer_cli_foreman-0.1.1-16.el6sat.noarch rubygem-hammer_cli_katello-0.0.4-14.el6sat.noarch How reproducible: 100% Steps to Reproduce: 1. hammer --help 2. hammer user --help 3. hammer organization --help Actual results: In all above cases: "[Foreman] username:" prompt is printed out. Expected results: No credentials prompt to appera, but directly the help page to be printed out. Additional info:
Created redmine issue http://projects.theforeman.org/issues/7408 from this bug
*** Bug 1143985 has been marked as a duplicate of this bug. ***
Additionally, even though the user is prompted for their Foreman credentials, no authentication takes place. I was able to still successfully run the help commands with nonsensical and/or nonexistent input for the Username and Password fields.
Moving to POST since upstream bug http://projects.theforeman.org/issues/7408 has been closed ------------- Anonymous Applied in changeset commit:17f7cc7b10698854ae05af738805ff8a3dfea607.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: RHEL66 / RHEL7 rubygem-hammer_cli_import-0.10.4-1.el7.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch rubygem-hammer_cli_katello-0.0.6-1.201411202238git7fa4778.git.0.a5a9308.el7.noarch rubygem-hammer_cli-0.1.3-1.201411181453git0c80831.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch
This bug is slated to be released with Satellite 6.1.
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://access.redhat.com/errata/RHSA-2015:1592