Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Description of problem:
When trying to login to katello/headpin shell using invalid credentials (invalid password/ non-existent userName), the shell shows up successfully instead of throwing an error.
(Credentials are authenticated only when a command is triggered on the katello/headpin shell)

How reproducible:
everytime

Steps to Reproduce:
1. # katello -u "invalidUsr" -p "invalidPass" shell
2. katello> org list

Actual results:
After 1. katello/headpin shell shows up
After 2. Invalid credentials

Expected results:
Should throw the "Invalid credentials" error after Step 1.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Created redmine issue http://projects.theforeman.org/issues/4896 from this bug

*** Bug 1166472 has been marked as a duplicate of this bug. ***

Upstream bug component is Uncategorized

Upstream bug component is Hammer

This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.