Project

General

Profile

Actions

Feature #8016

closed

Ability to use tokenized authentication to hammer in lieu of username/password in configuration file.

Added by Dominic Cleal over 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Hammer core
Fixed in Releases:
Found in Releases:
In Kanboard:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1154382
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):
rubygem-hammer_cli-0.1.1-12.el6sat.noarch

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:


Related issues 7 (0 open7 closed)

Related to Foreman - Feature #1301: Consider adding a per-user API keyClosedTimo GoebelActions
Related to Hammer CLI - Feature #13602: OAuth Support for HammerClosedActions
Related to Foreman - Feature #17487: Allow sessions for API callsClosedTomáš Strachota11/25/2016Actions
Related to Hammer CLI CSV - Bug #17624: session api breaks hammer csvClosedThomas McKay12/10/2016Actions
Related to Hammer CLI - Bug #17650: Basic authentication overrides any error with "Invalid username or password"ClosedTomáš Strachota12/13/2016Actions
Has duplicate Hammer CLI - Feature #8888: hammer auth should support token based authenticationClosedTomáš StrachotaActions
Blocks Hammer CLI - Feature #8923: Ability to use Negotiate/Kerberos authentication to API and hammerClosedOndřej EzrActions
Actions

Also available in: Atom PDF