dotnet list package --outdated returns 401 about artifacts-credprovider

[bteamsoftware]

This is not fixed

[JCC13]

I am still seeing this issue

[satbai]

Thanks for reporting, I can reproduce this on Windows. Needs investigation on what is special about the dotnet list command.

[MonkeyTennis]

I am seeing exactly this issue. Has this definitely been fixed in the latest version of the dotnet executable?

[shyambhiogade]

i still see this issue

[sebandraos]

With dotnet version 3.0.100-preview7-012821 and latest credential provider, the --interactive flag appears to work in:
dotnet list package --outdated --interactive --source '...AzureDevOpsFeed...'
and triggers a browser-based auth sequence. However it appears that it doesn't use the PAT for reauth and therefore the exact same command repeated immediately fails with the same 401. The same is true using Environment Variables to store the PAT.

This is blocking a certain phase of our CI so it would be great to get any available updates on this.

[satbai]

Dotnet has a fix for this in the latest version so closing the issue.