telerik · yordan-mitev · Sep 9, 2025 · Sep 9, 2025
@@ -21,11 +21,40 @@
 
 #end
 
+#generate-nuget-api-key
+
+As the Telerik NuGet server requires authentication, the first step is to obtain an API key that you will use instead of a password. Using an API key instead of a password is a more secure approach, especially when working with [.NET CLI](#use-the-net-cli) or the [`NuGet.Config` file](#edit-the-nugetconfig-file).
+
+1. Go to the [NuGet Keys](https://www.telerik.com/account/downloads/nuget-keys) page in your Telerik account.
+1. Click **Generate New Key +**.
+1. In the **Key Note** field, add a note that describes the API key.
+1. Click **Generate Key**.
+1. Select **Copy and Close**. Once you close the window, you can no longer copy the generated key. For security reasons, the **NuGet Keys** page displays only a portion of the key.
+1. Store the generated NuGet API key as you will need it in the next steps.
+
+Whenever you need to authenticate your system with the Telerik NuGet server, use `api-key` as the username and your generated API key as the password.
+#end
 
 #add-nuget-feed
 ## Step 3: Add the Telerik NuGet Feed to Visual Studio
 
-In this tutorial, you will use the [Telerik NuGet feed](slug:installation/nuget) to download the UI for Blazor components. This NuGet feed is private and requires you to authenticate with your Telerik user name and password:
+In this tutorial, you will use the [Telerik NuGet feed](slug:installation/nuget) to download the UI for Blazor components. This NuGet feed is private and requires you to authenticate with a NuGet API key.
+
+To generate your NuGet API key:
+
+1. Go to the [NuGet Keys](https://www.telerik.com/account/downloads/nuget-keys) page in your Telerik account.
+
+1. Click **Generate New Key +**.
+
+1. In the **Key Note** field, add a note that describes the API key.
+
+1. Click **Generate Key**.
+
+1. Select **Copy and Close**. Once you close the window, you can no longer copy the generated key. For security reasons, the **NuGet Keys** page displays only a portion of the key.
+
+1. Store the generated NuGet API key as you will need it in the next steps.
+
+Next, add the Telerik NuGet feed to Visual Studio:
 
 1. In Visual Studio and go to **Tools** > **NuGet Package Manager** > **Package Manager Settings**.
 
@@ -37,9 +66,9 @@ In this tutorial, you will use the [Telerik NuGet feed](slug:installation/nuget)
 
 ![Add the Telerik NuGet Feed in Visual Studio](images/telerik-nuget-feed.png)
 
-1. Whenever Visual Studio displays a dialog to enter credentials for `nuget.telerik.com`, use your Telerik account email and password.
+1. Whenever Visual Studio displays a dialog to enter credentials for `nuget.telerik.com`, use `api-key` as the username and your NuGet API key as the password.
 
->tip For alternative NuGet package download options, check the [Workflow article](slug:getting-started/what-you-need). You can also [authenticate with `nuget.telerik.com` with an API key](slug:installation/nuget#use-nuget-api-key).
+>tip For alternative NuGet package download options, check the [Workflow article](slug:getting-started/what-you-need).
 
 #end
 

@@ -10,32 +10,15 @@ position: 10
 
 This article describes how to use token-based authentication for the Telerik NuGet feed. You will learn how to create and use NuGet API keys to restore Telerik NuGet packages in your Continuous Integration (CI) workflow.
 
-The [Telerik NuGet server](slug:installation/nuget) provides two ways to authenticate:
-
-* Basic authentication with your Telerik username and password.
-* Token-based authentication with a NuGet API key.
-
-When you need to restore the [Telerik NuGet packages](slug:getting-started/what-you-need#nuget-packages) as part of your CI, a NuGet API key is the more secure way to authenticate. This method does not require you to provide your Telerik credentials anywhere in the CI workflow. A NuGet Key has a limited scope and can be used only with the Telerik NuGet server. If any of your NuGet keys is compromised, you can quickly delete it and create a new one.
-
+When you need to restore the [Telerik NuGet packages](slug:getting-started/what-you-need#nuget-packages) as part of your CI, using NuGet keys provides a secure way to authenticate. This method does not require you to provide your Telerik credentials anywhere in the CI workflow. A NuGet Key has a limited scope and can be used only with the Telerik NuGet server. If any of your NuGet keys is compromised, you can quickly delete it and create a new one.
 
 ## Generating NuGet Keys
 
-1. In your Telerik account, go to the [**Manage NuGet Keys**](https://www.telerik.com/account/downloads/nuget-keys) page.
-
-    ![Manage NuGet Keys](../deployment/images/manage-nuget-keys.png)
-
-1. Click **Generate New Key**.
-
-1. Enter a name for the NuGet Key and click **Generate Key**.
-
-1. To copy the key, click **Copy and Close**. Once you close the popup dialog, you can no longer copy the generated key. For security reasons, the **NuGet Keys** page displays only a portion of the key.
-
-    ![Copy Generated NuGet Key](../deployment/images/copy-nuget-key.png)
-
+@[template](/_contentTemplates/common/get-started.md#generate-nuget-api-key)
 
 ## Storing NuGet Keys
 
->warning Never check in Telerik account credentials or a NuGet API key with your source code or leave them publicly visible in plain text (for example, in a `NuGet.Config` file). A NuGet key is valuable and bad actors can use it to access the NuGet packages that are licensed under your account. A key abuse can lead to a review of the affected Telerik account.
+>warning Never check in a NuGet API key with your source code or leave them publicly visible in plain text (for example, in a `NuGet.Config` file). A NuGet key is valuable and bad actors can use it to access the NuGet packages that are licensed under your account. A key abuse can lead to a review of the affected Telerik account.
 
 To protect the NuGet Key, store it as a secret environment variable. The exact store steps depend on your workflow and environment:
 

@@ -48,7 +48,7 @@ This article explains how to get the <a href = "https://www.telerik.com/blazor-u
 
 2. Install the Telerik Blazor NuGet package:
 
-   1. Select the `telerik.com` **Package source** that you [added earlier](#step-3-add-the-telerik-nuget-feed-to-visual-studio). As this is a private NuGet feed, you must authenticate with your [Telerik account](https://www.telerik.com/account/) user name and password.
+   1. Select the `telerik.com` **Package source** that you [added earlier](#step-3-add-the-telerik-nuget-feed-to-visual-studio). As this is a private NuGet feed, you must authenticate using `api-key` as the username and [your NuGet API key](#step-3-add-the-telerik-nuget-feed-to-visual-studio) as the password.
    1. Select the **Browse** tab, find the `Telerik.UI.for.Blazor` NuGet package, and click **Install**.
 
    ![Add Telerik Blazor Package to Client Project](images/add-telerik-nuget-to-client-app.png)

@@ -62,7 +62,7 @@ This article explains how to use the Telerik UI for Blazor components in a Blazo
 
 1. Install the Telerik Blazor NuGet package:
 
-   1. Select the `telerik.com` **Package source** that you [added earlier](#step-3-add-the-telerik-nuget-feed-to-visual-studio). As this is a private NuGet feed, you must authenticate with your [Telerik account](https://www.telerik.com/account/) username and password.
+   1. Select the `telerik.com` **Package source** that you [added earlier](#step-3-add-the-telerik-nuget-feed-to-visual-studio). As this is a private NuGet feed, you must authenticate using `api-key` as the username and [your NuGet API key](#step-3-add-the-telerik-nuget-feed-to-visual-studio) as the password.
    1. Select the **Browse** tab, find the `Telerik.UI.for.Blazor` NuGet package, and click **Install**.
 
 ## Step 5: Enable the Blazor UI Components

@@ -20,14 +20,17 @@ You can set up the remote Telerik NuGet feed in the following ways:
 * [Use the .NET CLI](#use-the-net-cli)
 * [Edit the Nuget.Config file](#edit-the-nuget-config-file)
 
->tip When working with the .NET CLI or editing the `NuGet.Config` manually, you can use your Telerik account credentials or a [NuGet API Key](#use-nuget-api-key). If you are logging in to telerik.com through single sign-on (SSO), use a [NuGet API Key](#use-nuget-api-key).
+Regardless of how you set up the Telerik NuGet feed, you must first [generate a NuGet API key](#generate-a-nuget-api-key) needed for the authentication.
 
->warning Never hard-code Telerik account credentials or NuGet API keys in a `NuGet.Config` file in a GitHub repository, Docker image, or any location that may be accessed by unauthorized parties. A NuGet key is valuable and bad actors can use it to access the NuGet packages that are licensed under your account. A credentials abuse can lead to a review of the affected Telerik account.
+>warning Never hard-code your Telerik NuGet API keys in a `NuGet.Config` file in a GitHub repository, Docker image, or any location that may be accessed by unauthorized parties. A NuGet key is valuable and bad actors can use it to access the NuGet packages that are licensed under your account. A credentials abuse can lead to a review of the affected Telerik account.
 
 For NuGet-related issues, see [NuGet Feed Troubleshooting](slug:troubleshooting-nuget).
 
 For information on automated builds, CI and CD, see [CI, CD, Build Server](slug:deployment-ci-cd-build-pc).
 
+## Generate a NuGet API Key
+
+@[template](/_contentTemplates/common/get-started.md#generate-nuget-api-key)
 
 ## Use Visual Studio
 
@@ -44,34 +47,35 @@ Refer to the [Microsoft documentation about using packages in Visual Studio](htt
 1. Click OK.
 
 1. Open a project that references a Telerik NuGet package. For example, generate one through our [New Project Wizard](slug:getting-started-vs-integration-new-project).
-    * Make sure to remove local `NuGet.Config` files from the solution that contain information about Telerik packages. 
-    
+    * Make sure to remove local `NuGet.Config` files from the solution that contain information about Telerik packages.
+
 1. Rebuild the solution.
 
-1. A Windows prompt will ask for the Telerik feed credentials. Enter your Telerik email and password.
-    * Check the Remember My Password checkbox.
-
-1. Your project should now build and restore all packages - including those from nuget.org and from Telerik.
-    * If you experience issues, see the [NuGet Feed Troubleshooting](slug:troubleshooting-nuget) article.
+1. In the Windows authentication prompt:
 
+    7.1. Enter `api-key` in the **User Name** field.
 
-## Use the .NET CLI
+    7.2. Enter your [NuGet API key](#generate-a-nuget-api-key) in the **Password** field.
+
+    7.3. Check the **Remember My Password** checkbox.
 
-When adding NuGet sources from the .NET CLI, the credentials are stored in the `NuGet.Config` file. The [password can be encrypted on Windows, but with limitations](#store-encrypted-credentials). You can use a plain text password, but for better security, [generate a NuGet API Key](#use-nuget-api-key), and use it with the .NET CLI instead of a password.
+1. Your project should now build and restore all packages—including those from nuget.org and from Telerik.
+    * If you experience issues, see the [NuGet Feed Troubleshooting](slug:troubleshooting-nuget) article.
 
-To add the Telerik NuGet package source with the .NET CLI, use the [`dotnet nuget add source`](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-add-source) command. This command creates or updates a `NuGet.Config` file for you, so you don't have to [edit it manually](#edit-the-nuget-config-file).
+## Use the .NET CLI
 
-The command below stores the password or NuGet API Key in plain text in the [global config file](https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior#config-file-locations-and-uses).
+To add the Telerik NuGet package source with the .NET CLI, use the [`dotnet nuget add source`](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-add-source) command. The command shown below creates or updates a `NuGet.Config` file for you, so you don't have to [edit it manually](#edit-the-nugetconfig-file):
 
-The backslashes `\` below enable multi-line commands for better readability in terminals that support them.
+* The command adds the Telerik NuGet source, uses your [NuGet API key](#generate-a-nuget-api-key) for authentication, and stores the API key in plain text in the [global config file](https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior#config-file-locations-and-uses).
+* The backslashes `\` enable multi-line commands for better readability in terminals that support them.
 
 >caption Use the .NET CLI to add the Telerik NuGet source
 
 ````SH.skip-repl
 dotnet nuget add source https://nuget.telerik.com/v3/index.json \
 --name TelerikOnlineFeed \
---username <TELERIK EMAIL or api-key> \
---password <TELERIK PASSWORD or NUGET API KEY> \
+--username api-key \
+--password <YOUR-NUGET-API-KEY> \
 --store-password-in-clear-text
 ````
 
@@ -82,20 +86,11 @@ If you have already stored the Telerik package source, you can update the config
 ````SH.skip-repl
 dotnet nuget update source "TelerikOnlineFeed" \
 --source "https://nuget.telerik.com/v3/index.json" \
---username <TELERIK EMAIL or api-key> \
---password <TELERIK PASSWORD or NUGET API KEY> \
+--username api-key \
+--password <YOUR-NUGET-API-KEY> \
 --store-password-in-clear-text
 ````
 
-### Store Encrypted Credentials
-
-The .NET CLI supports NuGet password encryption only on the Windows platform. Note that [the encrypted password in the `NuGet.Config` file will work only for one user and one machine](https://learn.microsoft.com/en-us/nuget/reference/nuget-config-file#packagesourcecredentials).
-
-If you [add the Telerik package source in Visual Studio](#use-visual-studio), the credentials will be encrypted and stored in the Windows Credential Manager on Windows and in the Keychain on macOS.
-
-You can read more about the options provided by the NuGet tooling in the <a href="https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file#packagesourcecredentials" target="_blank">packageSourceCredentials section of the NuGet.Config reference</a> article by Microsoft. Note the difference between the `password` and `cleartextpassword` options. 
-
-
 ## Edit the NuGet.Config File
 
 NuGet package sources and other settings are stored in a `NuGet.Config` file. You can read more about the file structure in the Microsoft article [NuGet.Config Reference](https://learn.microsoft.com/en-us/nuget/reference/nuget-config-file).
@@ -106,7 +101,7 @@ To edit a `NuGet.Config` file and add the Telerik feed, you need to:
 
 1. Ensure you are editing the [correct and desired config file](https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior#config-file-locations-and-uses). You can also create a new one with the [`dotnet new nugetconfig` command](https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-new).
 
-2. Add the Telerik package source to the config file. Use plain text credentials, because the .NET Core NuGet tooling does not fully support encrypted credentials. Here is an example of how your `NuGet.Config` file can look like:
+2. Add the Telerik package source to the config file. For the authentication, use your [NuGet API key](#generate-a-nuget-api-key) as a password and `api-key` as a username. Here is an example of how your `NuGet.Config` file can look like:
 
 ````XML.skip-repl
 <?xml version="1.0" encoding="utf-8"?>
@@ -119,25 +114,13 @@ To edit a `NuGet.Config` file and add the Telerik feed, you need to:
     </packageSources>
     <packageSourceCredentials>
     <TelerikOnlineFeed>
-        <add key="Username" value="<TELERIK EMAIL or api-key>" />
-        <add key="ClearTextPassword" value="<TELERIK PASSWORD or NUGET API KEY>" />
+        <add key="api-key>" />
+        <add key="YOUR-NUGET-API-KEY" />
     </TelerikOnlineFeed>
     </packageSourceCredentials>
 </configuration>
 ````
 
-## Use NuGet API Key
-
-There are two ways to authenticate with the Telerik NuGet server when you add the Telerik NuGet source [with the .NET CLI](#use-the-net-cli) or [edit the `NuGet.Config` file manually](#edit-the-nuget-config-file):
-
-* Use your Telerik account email as the username, and your Telerik password.
-* Use `api-key` as the username and your personal [NuGet API Key](slug:deployment-nuget) as the password.
-
-You can [generate your Telerik NuGet API Key on telerik.com](https://www.telerik.com/account/downloads/nuget-keys). Read more about [using NuGet API Keys in different environments](slug:deployment-nuget).
-
-> Always use the NuGet API Key in plain text.
-
-
 ## Package Source Mapping
 
 The `Telerik.UI.for.Blazor` NuGet package and most of its dependencies reside on `nuget.telerik.com`. On the other hand, the [Telerik icon packages](slug:common-features-icons) and the [`Telerik.Licensing` package](slug:installation-license-key) reside on `nuget.org`. The correct [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping) configuration should be similar to the one below.
@@ -173,7 +156,6 @@ The `Telerik.UI.for.Blazor` NuGet package and most of its dependencies reside on
 </configuration>
 ````
 
-
 ## Access NuGet Packages behind Firewall
 
 To access the Telerik NuGet feed behind a firewall that restricts outgoing requests, you may need to allow the following domains:
@@ -183,12 +165,6 @@ To access the Telerik NuGet feed behind a firewall that restricts outgoing reque
 
 The firewall must allow some of the requests to be redirected from `nuget.telerik.com` to `downloads.cdn.telerik.com`.
 
-
-## Obsolete Telerik NuGet URL
-
-The NuGet v2 server at `https://nuget.telerik.com/nuget` was sunset in November 2024 and is no longer available. The v3 protocol offers faster package searches and restores, improved security, and more reliable infrastructure. To redirect your feed to the NuGet v3 protocol, all you have to do is to change your NuGet package source URL to `https://nuget.telerik.com/v3/index.json`.
-
-
 ## Troubleshooting
 
 See the [NuGet Troubleshooting](slug:troubleshooting-nuget) article for tips about common pitfalls when working with the Telerik NuGet feed.