Packages 403 error with full access PAT #53226
Replies: 2 comments 1 reply
-
Do you need to click the Configure SSO button? If you're using SSO? |
Beta Was this translation helpful? Give feedback.
-
Thanks for the response @wittml This turned out to be an issue with whitelisting the company IP. Turning the whitelist off stopped the error happening. I re-enabled it a couple of days later and things carried on working so I'm not sure what was going wrong. I spoke with support who said make sure any whitelist is set up at the enterprise and organisation level though at the time of it becoming an issue those settings hadn't been updated in a long time. Sometimes "Turn it off and on again" really is the solution ^^ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
We’re currently having a problem where we can’t access our nuget repo using our Personal Access Tokens and are getting a 403 error when trying to access.
The system previously was working correctly and as far as I know nothing has changed on our side. It is affecting multiple devs.
A PAT has been created, for testing it has been assigned every permission available.
The Package Source is declared in NuGet.config called “github”
Opening a browser and navigating to https://nuget.pkg.github.com/Witherslack-Group-Developers/index.json
Enter username and PAT
It returns the JSON
So the PAT seems to work.
However when trying to list the sources via command line it gives a forbidden exception
nuget search -Source github
So it looks like the token authenticates but is failing to the authorised to look at the packages even though all permissions have been assigned to the PAT.
Any ideas on what might have changed?
Beta Was this translation helpful? Give feedback.
All reactions