Nuget with Artifactory. Key not valid for use in specified state

Question

I am using Artifactory as NuGet repository to store all the nuget packages. When we use this Artifactory link as source, the package Manager in Visual Studio prompts for credentials and worked very fine. As soon as we moved to build machine (with out VS) and try to build application it is throwing error :

.nuget\NuGet.targets(100,9): error : Key not valid for use in specified state.

I added source with -user -password and put config at local user location. I tried with ClearText password and encrypted password both are throwing same error.

Am I missing anything here? Please advice.

Answer 1

I believe the error isn't related to Artifactory. The issue NuGet reports is related with encrypting/decrypting user credentials in nuget.config files.

I encountered the error when I tried to set apiKey for a repo:

NuGet setapikey user:pwd -Config .\NuGet.test.Config -Source .\packages

NuGet reported "Key not valid for use in specified state". I had NuGet.config file located near NuGet.test.Config. That nuget.config contained packageSourceCredentials section with credentials of other user (than one which was passed to setapikey). After I remove that credentials from nuget.config the error gone.

Answer 2

I encountered the same error when I logged into Windows using a new user account (story: our network admin at our company had removed our users due to an infection by a ransomware and created a new user account for each of us).

We have a local nuget server at our company (created using free Nuget Server).

As @Jinsoo stated, I needed to remove the nuget settings in Nuget.Config (at %AppData%/Roaming/Nuget folder) and set again the apikey for our nuget source using such a command:

nuget setApiKey abcdefghijklmn -Source http://www.our-company-nuget-server.com/nuget

After that I was able again to issue 'nuget push' commands.

Answer 3

Please check Nuget.Config in %AppData%\NuGet You may want re-create it in order to resolve the issue.

FYI, I had the same problem with my build agent, the issue is resolved by removing "nuget.config" in "C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\NuGet"