Description of problem:
This RFE requests the ability to configure hammer with either
* a token for login that is separate from the username/pass OR
* a session based credential cache so that the user can be prompted for login once at the beginning of their CLI session.
The goal is to keep the user from placing an administrative username/password within hammer's configuration file, in cleartext.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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/8016 from this bug
Reset docs contact <> daobrien
This would also allow persistent authentication for the REST API?
Upstream bug assigned to firstname.lastname@example.org
When resolving this bugzilla, please refer to any associated duplicates for additional input.
*** Bug 1380045 has been marked as a duplicate of this bug. ***
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/8016 has been resolved.
@ Satellite 6.3 snap 27
# hammer auth login
> [Foreman] Username: admin
> [Foreman] Password for admin:
# hammer auth status
> Session exists, currently logged in as 'admin
# hammer domain list (That didnt prompt for passwd)
ID | NAME
13 | BqgPSNLeQt
10 | FyWhgdcbSn
11 | GbqGiKuCws
18 | hCbPdswEni
12 | ibNwVTpdkU
9 | KktExDTarl
19 | lab.bos.redhat.com
14 | LoUVeZpkrC
15 | nSMsOicbPH
16 | OFKLpavbjh
17 | xQOQIFghpj
# hammer auth logout
> Logged out.
So the sessionized(tokenized) authentication is working as expected. Changing the state of bug to verified.
Note: This tokenized auth doesnt works with curl as mentioned in comment 9.
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.
*** Bug 1299016 has been marked as a duplicate of this bug. ***