<![CDATA[PyPI connector to Azure Artifacts returns 401, same URL and PAT work with curl]]>Hi there! I have some problems hooking up our Azure Artifacts pypi feed to Proget for a smooth transition from Azure Artifacts to Proget, wonder if you have some input :)

ProGet 2026.11 (Build 19), Basic Edition. PyPI feed with a connector to an Azure Artifacts PyPI feed:

  • Connector URL: https://pkgs.dev.azure.com/<org>/_packaging/<feed>/pypi (simple path left at the default simple/)
  • Authentication: Basic, user name azure, password = Azure DevOps PAT with Packaging (Read)

Requesting a package through the ProGet feed returns "Package not found", and the Diagnostic Center logs:

Connector error: The remote server returned an error: (401) Unauthorized.
System.Net.WebException ... at Inedo.ProGet.Feeds.Pypi.PypiConnector.GetSimpleProjectDetailAsync(String projectName, ...) PypiConnector.cs:line 102

The same request from the ProGet host's network with curl succeeds: curl -u azure:<PAT> https://pkgs.dev.azure.com/<org>/_packaging/<feed>/pypi/simple/<package>/ returns 200, for both the HTML and the application/vnd.pypi.simple.v1+json Accept header. With a valid PAT Azure returns 404 for wrong paths, so the 401 means the connector's credentials are not accepted. Re-entering the password in the UI and via the management API makes no difference. Azure's 401 challenge lists three schemes in this order: WWW-Authenticate: Bearer authorization_uri=..., Basic realm="...", TFS-Federated. Is it possible the Basic credentials are only sent after a challenge and the Bearer entry is picked instead? Is there a way to make the PyPI connector send Basic credentials preemptively?

Cheers
Carl

]]>https://forums.inedo.com/topic/5850/pypi-connector-to-azure-artifacts-returns-401-same-url-and-pat-work-with-curlRSS for NodeMon, 05 Oct 2026 23:04:44 GMTMon, 05 Oct 2026 11:03:08 GMT60<![CDATA[Reply to PyPI connector to Azure Artifacts returns 401, same URL and PAT work with curl on Mon, 05 Oct 2026 17:34:51 GMT]]>Hi @carl.westman_8110,

I ran a test against our test Dev Ops instance. I created a connector and I used basic authentication with my Microsoft account username (my email) as the username and the PAT as the password. I found it was finding my package, but ADO's simple API was not returning the file list which is causing our connector to skip over it. We are currently investigating this further.

As a work around, have you tried importing those packages into your ProGet feed? You can do that by using Import Package -> Download Package from Another Source. That will allow you to import all the packages and version from your ADO artifact feed.

Thanks,
Rich

]]>https://forums.inedo.com/post/20109https://forums.inedo.com/post/20109Mon, 05 Oct 2026 17:34:51 GMT