Feature #1301
Consider adding an API key
| Status: | New | Start: | 11/08/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | API | |||
| Target version: | - | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 1 (View) |
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.
History
Updated by Ohad Levy 10 months ago
- Target version set to 1.1
would the oauth implementation would suffice ?
Updated by Brian Gupta 10 months 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).
Updated by alan mcginlay 6 months ago
- File api_token.png added
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.
