Learn more about these different git repos.
Other Git URLs
Currently you need to have at least 1 project to have an API key. So if you want to create a new project using the API, you need to manually create a project to generate a token.
The API keys should be generated from the user's settings page.
If we go work on this, it would be great if we could use the standard OAuth tokens that Fedora has in staging and will be getting in production soon.
We'll need to prioritize this a bit as this will be needed for like CI integration across multiple projects
Metadata Update from @pingou: - Issue tagged with: RFE
+1, I have push rights to freeipa and almost full access to freeipa pagure, but I cannot create a token for accessing freeipa pagure issues. (Admin of freeipa had to create a one for me )
Right, also an issue is that a token generated in the project settings is the project. So if multiple people has tokens generated and assigned then there is no way to tell who did what change - no audit.
That is actually not true, API token are per users and only the user's API token are shown on the settings page.
But users that has no admin rights cannot create tokens for that project (so I tested with my token created in my project I haven't had access to other projects)
Correct, currently the API keys are per project and per user. We'll need to offer a way to have it just per user :)
Metadata Update from @pingou: - Issue assigned to pingou
Fixed in https://pagure.io/pagure/pull-request/2055
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.