nuget.exe push/delete won't use API Key

[spadapet]

Using version 3.4.3.854

REPRO

• Start with the default nuget.config file in %appdata%\nuget that only has nuget.org as a source
• In a browser, log into your nuget.org account and follow the instructions to set an apikey:
• nuget.exe setApiKey XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
• Try to unlist one of your packages:
• Example 1: nuget.exe delete foo 99.99 -Source nuget.org
• Example 2: nuget.exe push foo.nupkg -Source nuget.org

RESULT
WARNING: No API Key was provided and no API Key could be found for 'https://www.nuget.org/api/v2/package'. To save an API Key for a source use the 'setApiKey' command.

EXPECT
I already did set the API Key according to the instructions. Unlisting works fine if I set the API Key for https://www.nuget.org/api/v2/package, but why do I need to do that?

NOTE
Same issue with myget.org

[yishaigalatzer]

@spadapet is this a regression?

[spadapet]

I tried the previous version (3.3.0.212) and it fails for an even more bizarre reason:

> nuget3.exe delete MyTestPackageX 2.0.2 -Source nuget.org
WARNING: No API Key was provided and no API Key could be found for 'https://api.nuget.org/v3/index.json'. To save an API Key for a source use the 'setApiKey' command.
Deleting MyTestPackageX 2.0.2 from the 'https://api.nuget.org/v3/index.json'.
Failed to process request. 'HTTP Version Not Supported'.
The remote server returned an error: (505) Http Version Not Supported..

Looks like this:

And then if I add the API Key for https://api.nuget.org/v3/index.json, it still fails:

So, the behavior is sort of better now since I can actually unlist. But I need to know to set the API Key for a specific packages URL

[spadapet]

Ah, it is a regression from nuget.exe 2.8.60717.93.

• nuget2.exe setApiKey [my key]
• nuget2.exe delete mytestpackagex 2.0.2

Works fine

[zhili1208]

the issue here is
nuget.exe setApiKey [mykey]
the default apikey config is key ="https://www.nuget.org", value =[mykey]
nuget.exe delete mytestpackagex 2.0.2
nuget try to find value of key "https://www.nuget.org/api/v2/package" in nuget.config, it return null.

[jmyersmsft]

Whether or not this is the same root cause as #2975 , that bug is not just a problem of inconsistent defaults, and it's not just a problem for nuget.org.

[zhili1208]

@jmyersmsft yes, this is not a problem for nuget.org, it's for all sources

[rrelyea]

Zhi found several dupes. Putting in beta3 for analysis.

[wallism]

I had the same issue today on v3.4.3.855.
I set the api key using the required command, then when I ran the push I got this warning:

WARNING: No API Key was provided and no API Key could be found for 'https://www.nuget.org/api/v2/package'

and was asked to login using username and password.

So the issue for me was, when I ran: nuget SetApiKey abc...def, I noticed that in the config file ("%Appdata%\Roaming\Nuget\NuGet.Config") it added a key for https://www.nuget.org, when I changed to to the full path it worked fine -> https://www.nuget.org/api/v2/package

So the bug appears to be in the SetApiKey command, not setting the correct key (for the push case anyway)

[emgarten]

@wallism get the latest nuget.exe 3.5.0 here: http://dist.nuget.org/index.html

If you are still seeing the bug open a new issue to track this.