[Bug]: dotnet nuget push not detecting apikey for 3rd party symbol server

[erdembayar]

NuGet Product Used

dotnet.exe

Product Version

n/a

Worked before?

No response

Impact

It bothers me. A fix would be nice

Repro Steps & Context

1. Set apikey for myget repo v3 index.
2. Create nupkg + snupkg.
3. Please do dotnet nuget push .\somepackage.1.1.0.nupkg --source myget
   It doesn't detect apikey for 3rd party symbol server, not sure if it's myget implementation issue or nuget.client issue. It looks workaround is pass actual apikey as parameter in cli.
   

As you can see in fiddler log it's missing apikey header.

4. Also do nuget push .\somepackage.1.1.0.nupkg -source myget then it asks for username.
   It looks workaround is pass actual apikey as parameter in cli.
   

Verbose Logs

No response

[kartheekp-ms]

AFAIK, NuGet checks if the third party package source supports publish symbols. If the third party package source can provide SymbolPackagePublish resource in the ServiceIndex then passing the symbol apikey via command line is not required.

https://github.com/NuGet/NuGet.Client/blob/d970aa3fd6d607642ceb0905498ec0d75a03562c/src/NuGet.Core/NuGet.Commands/CommandRunners/PushRunner.cs#L61-L67

Jm2c, it is not a NuGet bug. Reference - https://docs.microsoft.com/en-us/nuget/api/symbol-package-publish-resource

[whatatripp]

Hi @kartheekp-ms @jeffkl

This definitely seems to be a bug in the client; I did not debug the code you linked to, but something is not being wired up.

ProGet provides a SymbolPackagePublish resource in the feed ServiceIndex, but the API key is not used. Here is snippet:

{"@id":"http://proget.localhost/nuget/nuggets/symbolpackage","@type":"SymbolPackagePublish/4.9.0"}

After setting an explicit API key for the */symbolpackage URL, this prompt goes away. It seems MyGet works the same way, and the API key is ignored.

We'd really appreciate if you could fix this, to make our mutual users/customers have an easier debugging experience :)

[erdembayar]

We'd really appreciate if you could fix this, to make our mutual users/customers have an easier debugging experience :)

Please upvote the original issue on top, we prioritize investigations based on community engagement such as comments and up-votes.