Feature #1301: Consider adding a per-user API key - Foreman

Custom queries

3.11.5 release DONE
3.11.5 release TODO
3.12.2 release DONE
3.12.2 release TODO
3.13.0 release DONE
3.13.0 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Feature #1301

closed

Consider adding a per-user API key

Added by Brian Gupta about 13 years ago. Updated about 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Timo Goebel

Category:

API

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/4597

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Many Rails apps support authentication via a per user API key. If it's not too much work, we may wish to add this as an option.

Files

api_token.png

View api_token.png

19.8 KB

API token page on an example gitlab site

alan mcginlay, 11/15/2012 06:43 AM

Related issues 7 (2 open — 5 closed)

Related to Foreman - Feature #1576: Implement oauth authentication and authorization	Closed			Actions
Related to Hammer CLI - Feature #8016: Ability to use tokenized authentication to hammer in lieu of username/password in configuration file.	Closed	Tomáš Strachota	10/21/2014	Actions
Related to Foreman - Feature #8852: add token-based authentication feature for API	New			Actions
Related to Foreman - Bug #18245: Enabling OAuth is too dangerous	New		01/25/2017	Actions
Related to Foreman - Feature #21394: add an api for personal access tokens	Closed	Timo Goebel		Actions
Related to Foreman - Feature #31080: Add UI for managing Personal Access Tokens	Closed	Kamil Szubrycht		Actions
Has duplicate Foreman - Feature #4331: allow for per-user oauth api keys	Duplicate		02/12/2014	Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Ohad Levy over 12 years ago

Target version set to 1.1

would the oauth implementation would suffice ?

Actions

Copy link

Updated by Brian Gupta over 12 years ago

Welll.. As I understand, Oauth is to allow external auth sources. (You need a third party oauth trusted authentication source, no?)

When I created this ticket, I was thinking of a native API key, that each user could generate and revoke for their own accounts, so they didn't have to bake their pw into scripts and what not... (Correct me if I am misunderstanding what you are proposing with Oauth).

Actions

Copy link