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 #1

Updated by Dominic Cleal over 9 years ago

  • Related to Feature #1301: Consider adding a per-user API key added
Actions #2

Updated by Dominic Cleal over 9 years ago

  • Category set to Hammer core
Actions #3

Updated by Tomáš Strachota over 9 years ago

  • Has duplicate Feature #8888: hammer auth should support token based authentication added
Actions #4

Updated by Jan Pazdziora over 9 years ago

  • Blocks Feature #8923: Ability to use Negotiate/Kerberos authentication to API and hammer added
Actions #5

Updated by Dominic Cleal about 8 years ago

Actions #6

Updated by Tomáš Strachota over 7 years ago

  • Target version set to 115
Actions #7

Updated by Marek Hulán over 7 years ago

  • Assignee set to Tomáš Strachota
  • Target version changed from 115 to 1.5.0

as we discussed yesterday, storing session ID might be enough, hammer would fallback to username/password credentials if session expired or no session was stored

Actions #8

Updated by Tomáš Strachota over 7 years ago

  • Status changed from New to Assigned
Actions #9

Updated by Marek Hulán over 7 years ago

  • Target version changed from 1.5.0 to 1.4.2
Actions #10

Updated by Marek Hulán over 7 years ago

  • Target version changed from 1.4.2 to 1.4.4
Actions #11

Updated by The Foreman Bot over 7 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/hammer-cli/pull/227 added
Actions #12

Updated by The Foreman Bot over 7 years ago

  • Pull request https://github.com/theforeman/hammer-cli-foreman/pull/269 added
Actions #13

Updated by Tomáš Strachota over 7 years ago

Actions #14

Updated by Marek Hulán over 7 years ago

  • Target version changed from 1.4.4 to 1.10.1
Actions #15

Updated by Anonymous over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #16

Updated by Thomas McKay over 7 years ago

  • Related to Bug #17624: session api breaks hammer csv added
Actions #17

Updated by Tomáš Strachota over 7 years ago

  • Related to Bug #17650: Basic authentication overrides any error with "Invalid username or password" added
Actions #18

Updated by Tomáš Strachota about 7 years ago

  • translation missing: en.field_release set to 235
Actions #19

Updated by Tomáš Strachota about 7 years ago

  • translation missing: en.field_release changed from 235 to 236
Actions

Also available in: Atom PDF