Add support for API token on organization/project

[pjechris]

API token is currently linked to a personal account. Making it a trouble when the owner is leaving the team.

It would be very useful to have API tokens for organizations and/or projects to mitigate this issue.

[dansiegel]

That is indeed a problem... I would add here that it is equally a problem from a security standpoint where I might belong to several organizations and a token I create now gives a project access to all of the organizations and apps that I have access to.

[aastlind]

Any news regarding this? Would love to see organization API tokens to be able to get away from person dependency.

[vanlooverenkoen]

I am currently using 1 api token per app only (Full access, read only). That is already possible.
It is not yet possible to create an api token on organization level.

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

This issue will now be closed because it hasn't had any activity for 15 days after stale. Please feel free to open a new issue if you still have a question/issue or suggestion.

[Manouli]

I think this need to be reopened.

[svendr]

This should be fixed. It's a pain working with app-level tokens, because these can't use company-level distribution groups. And using user tokens for multiple apps and even companies is a big security issue.

[gretzki]

Can't stress enough how important this feature is.
Using user-level tokens in our company means giving the CI/CD job access to 100+ companies.
Using app-level tokens is not a solution, since then only app-level distribution groups are accessible, not company-level ones.
Please reconsider this feature @microsoftopensource