Telerik NuGet keys - Rotating Telerik Service Account for a build NuGet server
|Product||Progress® Telerik® UI for ASP.NET AJAX|
Learn how to deal in a scenario with a build server when you have to store the private Telerik NuGet credentials.
Use case questions: Is it possible to get a secondary login for the Telerik private NuGet that is not tied to a specific user account login?
We would like to use the NuGet feed on a build server and are concerned about the account login getting rotated and not updated on the build server.
Until now, you could only use your Telerik account’s credentials to authenticate with the Telerik NuGet server. This is fine when the environment is your own dev machine but can be problematic in CI environments like Azure DevOps/GitHub Actions, or a colleague’s machine who needs to restore packages to build a project but doesn't use them directly (e.g., QA, designer, or a build user account, etc.).
That is why we introduced the new NuGet Keys feature available in your account under https://www.telerik.com/account/downloads/nuget-keys.
You can now generate a unique key that can be used to authenticate with the Telerik NuGet server to restore packages in your CI (Continuous Integration) or desktop environment.
- Announcing NuGet Keys
- (First Steps by Installing from a NuGet Package)[https://docs.telerik.com/devtools/aspnet-ajax/getting-started/first-steps-nuget].