-
Notifications
You must be signed in to change notification settings - Fork 80
docs(common): Improve NuGet 401 documentation #2610
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.
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
Conversation
|
Hello @dimodi, Check the below option if you would like to automatically generate PR to production. The automation uses the branch for the cherry-pick, and then will delete the branch. Please, do not delete it manually.
|
|
Here you are the link to your PR to production: 2615 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed.
Having single H3 sub-sections is somewhat odd (similar to having one-item lists). If the reason is that you want to be able to link to these, I would consider alternative ways to implement anchors.
| If your credentials are correct and your license includes the requested product and version, then the password probably contains special characters. You need to escape these characters or the authentication can fail on the NuGet server. For example, a common character you must escape is the ampersand (`&`); however, the character causing the issue may be as unique as the section character (`§`). | ||
| `Error 401 Unauthorized` means that the Telerik NuGet server received invalid credentials. There may be different reasons for that: | ||
|
|
||
| * No provided credentials |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a list of mixed items, if at least one item is a complete sentence, then all items should end with a period. (Source.)
| * Using an invalidated (removed) [Telerik NuGet API key]({%slug installation/nuget%}#use-nuget-api-key), which no longer exists in <a href="https://www.telerik.com/account/downloads/nuget-keys" target="_blank">your Telerik account</a>. | ||
| * Using a valid Telerik NuGet API key with the wrong username. It must be `api-key`. | ||
|
|
||
| An easy way to verify your credentials is to [access the Telerik NuGet server directly in the web browser](#tips-for-handling-common-nuget-issues). Then, depending on your setup, check or update your credentials in: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be more helpful and logical for the link to point to #verify-nuget-credentials-and-package-access or to the actual NuGet server.
No description provided.