Access Packages via token on organizational level #130895
Replies: 1 comment
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
For many organizations nowadays it's necessary to access packages (npm, docker, ...) from systems like Vercel or other (custom ones as well).
Right now the only option is to authentication with a personal access token to read from the registry. Which means organizations have to add a bot user to their organization to create a classic PAT. In my opinion it should be possible to cover the access of private packages via GitHub Apps or some kind of "Personal Access Token" on orgnization level ("OAT - Organizational Access Token").
I've read that the general concept of having another option to authenticate is already a feature request. (https://github.com/orgs/community/discussions/48186#discussioncomment-5123890). But since then some time went by and I wanted to use this discussion to make aware of the urge of this feature.
Beta Was this translation helpful? Give feedback.
All reactions