[Bug]: Error message for dotnet nuget push with apikey from another machine need improvement

[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

If you create apikeys with "nuget setapikey xxxxx -source somesource" then it creates apikeys section in nuget.config.
If you copy whole repo including nuget.config into another machine, then try push nupkg then it gives me error: Key not valid for use in specified state. Reason is encrypted apikey is tied to machine, in another machine it need to regenerate.
It's not helpful, it should give us better message for why it's failing.

Verbose Logs

No response

[kartheekp-ms]

My understanding is that it is hard to distinguish if an apikey is invalid because of user error or if it has been generated on another machine.

[bvamos]

How to resolve this issue if we are running nuget push in Docker containers?

[erdembayar]

How to resolve this issue if we are running nuget push in Docker containers?

Please create a separate issue with more details. Where are you pushing from docker container and dotnet sdk version etc?