dotnet list <SOLUTION> package --vulnerable/--outdated/--deprecated fails with Azure Artifacts Credential Provider

[josundt]

dotnet list package --vulnerable/--outdated/--deprecated fails with Azure Artifacts Credential Provider

from home.

[josundt]

@pkamphuis @martinrrm
I tested again today; and the problem has disappeared.
I am not exactly sure what may have solved it, but I'm aware of the following changes on my machine:

• .NET SDK has been upgraded from 8.0.205 to 8.0.300.
• NuGet CLI (Microsoft.NuGet) was upgraded (using winget) from ? to 6.10.0.107

Not sure if the NuGet CLI is used in this process but thought I'd mention it.

[martinrrm]

This is probably related to dotnet/sdk#38306, we fixed a regression related to the relative paths, most likely we are not handling the exception correctly. This fix is in 8.0.3x, can you try it? Thanks!

[pkamphuis]

Is this fix in DotNet sdk 8.0.203? (runtime 8.0.3)

I am still experiencing this issue. Both on a solution or a project. As soon as I include --include-transitive it start repetitive authentication device flows. It seems be done for each referenced project in de project. I end up with dozens of created PAT tokens in my Azure Devops account. So it appears to create a token for each individual project.

[pkamphuis]

What information is needed to investigate this issue?

From what I can see, does the credential provider what is expected. Triggering a device flow login. I authenticate. A PAT token is created with the correct scope. However in the dotnet restore output it still indicate unable to load service index with a 401. After which it goes in the next device flow to retry

[josundt]

@pkamphuis @martinrrm
This is still not fixed (.NET 8.0.4/SDK 8.0.204).

I am still not sure if this is an Azure DevOps Credential Provider problem, therefore I also have an open issue in their GitHub repo, and I have just now added some repro information to that issue.

Can you please read that information and investigate this further?
This case should not be closed before the problem is solved!

As far as I can tell you should by now have all the required information to reproduce this.