Restoring a nuget package hosted in Github Packages returns a 403

[pseudosma]

Select Topic Area

Bug

Body

I used GitHub Actions to publish a package to my organization's packages (using the built-in GITHUB_TOKEN) but I'm unable to add it to my local repo. I keep seeing 403 errors when attempting to connect. I've followed the guide for setting up a classic PAT to the letter and still am unable to connect.

I've also tried this in Visual Studio's nuget Package Manager, the Nuget CLI, and the dotnet nuget CLI just to rule out anything wrong with the tools I'm using.

I've gone through several online discussions, and I've been able to rule out a few things that other users ran into:

• IP whitelisting is not an issue: https://github.com/orgs/community/discussions/53226

• This hasn't been caused by a service outage: https://github.com/orgs/community/discussions/152536

• I have been using ClearTextPassword in the nuget.config: https://github.com/orgs/community/discussions/26974

The other things I've confirmed:

• The classic token has sufficient permissions. I've been testing one with ALL permissions just to rule out any single one causing problems.

• My organization uses SSO, and the SSO option is enabled for this token.

• My package inherits access from the parent repository that it was published from. I'm an admin on that repo, so I should be able to pull from this with my PAT.

The other thing that I notice is that the PAT I created can connect to my personal packages, but not my org's packages.... if I change the nuget source from https://nuget.pkg.github.com/myOrg/index.json to https://nuget.pkg.github.com/myUser/index.json, I don't see a 403. And this is despite having the SSO authorized on the token. So, I should be able to reach my org's packages with this PAT but I can't.

Any ideas on other things I can try?

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[henrychris]

+1
All my action builds are failing to restore for this reason. Generated a new token even, but no luck.