Hi, I have my license on
https://www.telerik.com/kendo-react-ui/my-license/
and trying to add KendoReact to an existing react application. When following instructions and running "npm install --save @progress/kendo-licensing", I get this error: "Unable to authenticate, need: Basic realm="Artifactory Realm""
PS C:\Users\NBKVCNE\source> cd pcoe
PS C:\Users\NBKVCNE\source\pcoe> npm install --save @progress/kendo-licensing
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\NBKVCNE\AppData\Roaming\npm-cache\_logs\2022-01-21T16_29_56_327Z-debug.log
1 Answer, 1 is accepted
Hello,
I see that this had occurred before last year as well.
This seems like an issue with the npm registry itself, please check details on a similar case here:
https://superuser.com/questions/1486347/getting-npm-err-unable-to-authenticate-need-basic-realm-artifactory-realm
If the issue still occurs, please send us a license file and we will check if there is any issue with it as well.
Regards,
Stefan
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.
Rank 1
The license file seems to be correct.
The error looks to be connected to the NPM registry, not the license.
If you have used other Kendo UI packages in the past, please check if this is not the reason for the error:
https://docs.telerik.com/kendo-ui/intro/installation/npm#kendo-ui-for-jquery-on-npm
`The Progress NPM registry was retired in favor of npmjs.com. To start using the default registry, remove the two lines which contain registry.npm.telerik.com from your .npmrc file.`
Rank 1
This is a new laptop so it will not have older versions of Kendo UI.
I looked at the page and was able to run this command: npm install --save kendo-ui-core
But running this command I get same 'unable to authenticate' error:
npm install --save @progress/kendo-ui@latest
In my .npmrc file, there are no two lines with 'registry.npm.telerik.com' in it. Here is what my .npmrc file looks like if it helps
@progress:registry=https://artifacts.horizon.bankofamerica.com/artifactory/api/npm/horizon-virtual-npm/
Thank you for the information.
This seems to be using a private registry for your company.
Please try installing react itself to confirm:
https://www.npmjs.com/package/react
If the same error occurs, that means that the entire access to npm is blocked and I can suggest speaking with our team on how the team accesses the npm packages.
Rank 1
React definitely works...been writing various sample apps, but I just ran this:
PS C:\Users\NBKVCNE\source\kendotest> npm i react
npm WARN @apideck/better-ajv-errors@0.3.2 requires a peer of ajv@>=8 but none is installed. You must install peer dependencies yourself.
npm WARN fork-ts-checker-webpack-plugin@6.5.0 requires a peer of typescript@>= 2.7 but none is installed. You must install peer dependencies yourself.
npm WARN tsutils@3.21.0 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
+ react@17.0.2
updated 1 package and audited 1399 packages in 7.974s
168 packages are looking for funding
run `npm fund` for details
found 5 moderate severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
Hello,
Thank you for the confirmation.
The .npmrc shows that you are using a private company registry `https://artifacts.horizon.bankofamerica.com/artifactory/api/npm/virtual-npm/`. That means that you only have access to the packages located in that registry.
There are two options in that case:
1) Check in the company with the team that supports that registry if they can add our packages as well.
2) Add an exception in the .npmrc for packages from our organization. There is such an exception already in the file but it is again setting the private registry. It needs to use the default npm registry.
As this is connected with the company policies that restrict access to all packages, I suggest speaking with the team in the company that is responsible for that and taking actions based on their recommendations.
That is not something we on the KendoReact side have any control over.