Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pass API Key when pushing to Azure DevOps #520

Closed
gep13 opened this issue Jul 4, 2020 · 0 comments
Closed

Pass API Key when pushing to Azure DevOps #520

gep13 opened this issue Jul 4, 2020 · 0 comments
Assignees
@gep13
Labels
Bug
Milestone
2.0.0

Comments

@gep13
Copy link
Member

gep13 commented Jul 4, 2020

Even though a Username/Password combination is used to authenticate to Azure DevOps, it is necessary to also set the API Key to "something", if not, then the following error occurs:

Response status code does not indicate success: 400 (Bad Request - The request to the server did not include the header X-NuGet-ApiKey, but it is required even though credentials were provided. If using NuGet.exe, use 
the -ApiKey option to set this to an arbitrary value, for example "-ApiKey AzureDevOps" (DevOps Activity ID: E67FE45D-B853-48ED-BBF0-3CB369B838A3)).
@gep13 gep13 added the Bug label Jul 4, 2020
@gep13 gep13 added this to the 2.0.0 milestone Jul 4, 2020
@gep13 gep13 self-assigned this Jul 4, 2020
gep13 added a commit that referenced this issue Jul 4, 2020
@gep13
(GH-520) Add random ApiKey
cb7db3f 
To set the X-NuGet-ApiKey header when pushing to sources like Azure
Artifacts.
@gep13 gep13 closed this as completed Jul 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gep13 gep13

Labels
Bug
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@gep13