Project

General

Profile

Feature #1301

Consider adding a per-user API key

Added by Brian Gupta over 9 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

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.

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
Api token

Related issues

Related to Foreman - Feature #1576: Implement oauth authentication and authorizationClosed
Related to Hammer CLI - Feature #8016: Ability to use tokenized authentication to hammer in lieu of username/password in configuration file.Closed2014-10-21
Related to Foreman - Feature #8852: add token-based authentication feature for APINew
Related to Foreman - Bug #18245: Enabling OAuth is too dangerousNew2017-01-25
Related to Foreman - Feature #21394: add an api for personal access tokensClosed
Related to Foreman - Feature #31080: Add UI for managing Personal Access TokensClosed
Has duplicate Foreman - Feature #4331: allow for per-user oauth api keysDuplicate2014-02-12

History

#1 Updated by Ohad Levy about 9 years ago

  • Target version set to 1.1

would the oauth implementation would suffice ?

#2 Updated by Brian Gupta about 9 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).

#3 Updated by alan mcginlay over 8 years ago

The way gitlab manages it would be ideal. Example api request:

GET http://example.com/api/v2/projects?private_token=QVy1PB7sTxfy4pqfZM1U

That would list out all the projects which the user with that private token has access to.

#4 Updated by Ohad Levy over 8 years ago

  • Target version deleted (1.1)

#5 Updated by Dominic Cleal over 7 years ago

  • Has duplicate Feature #4331: allow for per-user oauth api keys added

#6 Updated by Dominic Cleal over 7 years ago

  • Related to Feature #1576: Implement oauth authentication and authorization added

#7 Updated by Dominic Cleal over 7 years ago

  • Subject changed from Consider adding an API key to Consider adding a per-user API key

#8 Updated by Dominic Cleal almost 7 years ago

  • Related to Feature #8016: Ability to use tokenized authentication to hammer in lieu of username/password in configuration file. added

#9 Updated by Dominic Cleal over 6 years ago

  • Related to Feature #8852: add token-based authentication feature for API added

#10 Updated by Dominic Cleal over 4 years ago

  • Related to Bug #18245: Enabling OAuth is too dangerous added

#11 Updated by Timo Goebel about 4 years ago

  • Status changed from New to Assigned
  • Assignee set to Timo Goebel

#12 Updated by The Foreman Bot about 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4597 added

#13 Updated by Timo Goebel almost 4 years ago

  • Related to Feature #21394: add an api for personal access tokens added

#14 Updated by Rahul Bajaj about 1 year ago

  • Status changed from Ready For Testing to Closed

#15 Updated by The Foreman Bot about 1 year ago

  • Pull request https://github.com/theforeman/foreman/pull/7806 added

#16 Updated by Kamil Szubrycht 10 months ago

  • Related to Feature #31080: Add UI for managing Personal Access Tokens added

#17 Updated by Kamil Szubrycht 10 months ago

  • Pull request deleted (https://github.com/theforeman/foreman/pull/7806)

Also available in: Atom PDF