Make the API key the primary NuGet auth method #1876
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yordan-mitev
requested review from
IvetNikolova,
dnikolov-prg,
petar-i-todorov and
todorarabadzhiev
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation to make API key authentication the primary and recommended method for accessing the Telerik NuGet server, replacing the previous username/password approach. The changes reflect new product management requirements that prioritize API key-based authentication for improved security.
- Removes references to username/password authentication throughout the documentation
- Adds comprehensive instructions for generating and using API keys
- Updates troubleshooting guides to recommend API key usage instead of password resets
Reviewed Changes
Copilot reviewed 6 out of 12 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| knowledge-base/troubleshooting-nuget.md | Updates troubleshooting instructions to use API keys and fixes broken anchor links |
| knowledge-base/nuget-feed-error-returned-unexpected-401-status-code.md | Replaces password reset instructions with API key authentication steps |
| knowledge-base/migrate-an-existing-asp-net-core-project-from-full-dotnet-framework-4-6-to-dotnet-core-2-2.md | Updates anchor link to match new installation documentation structure |
| getting-started/installation/using-nuget-keys.md | Renames "NuGet Keys" to "API Keys" throughout and updates environment variable names for consistency |
| getting-started/installation/installation-approaches.md | Restructures NuGet installation section into three clear steps, adding API key generation as the first step |
| getting-started/installation/adding-private-nuget-feed.md | Adds API key generation section and removes password special character handling instructions |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
todorarabadzhiev
previously approved these changes
Oct 29, 2025
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
todorarabadzhiev
deleted the
authenticate-nuget-with-api-key-no-password
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the latest requirements set by our PMs, the only documented authentication approach for the Telerik NuGet server must be the authentication with an API Key.