Hi,We are using infragistics "@infragistics/igniteui-angular": "~13.2.16" in our packge.json file.We generated the token for one of the user accounts, and configured registry, username (email), token and always-true in .npmrc file.Also, we have configured the varibales in in the pipeline. (as per the link https://ko.infragistics.com/products/ignite-ui-angular/angular/components/general/ignite-ui-licensing#azure-pipelines-configuration). But still, when the CI pipelines runs, it fails with below errorError during npm install in Azure DevOps CI pipelineGET 401 https://packages.infragistics.com/npm/js-licensed/@infragistics%2figniteui-angular 523ms (cache skip)npm verb stack HttpErrorGeneral: 401 Unauthorized - GET https://packages.infragistics.com/npm/js-licensed/@infragistics%2figniteui-angular - UnauthorizedIf we relace "~" with "^", then it is giving 404 error.npm http fetch GET 404 https://registry.npmjs.org/@infragistics%2figniteui-angular 245ms (cache skip).It is working fine locally. Can you please let us in this, how can we download the package in azure pipeline?
Hello,
I have been looking into the provided details and what I could say is that error 401 usually means that you do not have access to the packages due to a lack of ‘_auth’ section or wrong token at the .npmrc file. Error 404 indicates that the npm is not configured and when installing our package, searches it under the npmjs.org repo(GET registry.npmjs.org/@infragistics....) instead of our private repository.
Having this in mind, my suggestion is to verify that you are setting '_auth' instead of 'auth' and the token and setup is correct in your .npmrc files and Azure.
If the issue still persists, please let me know, so I could create a private case in order to investigate this further.
Looking forward to hearing from you.
Thank you for your cooperation.
Sincerely,Teodosia HristodorovaSoftware Developer
Hi Team, Any update on this or anything we can try to identify the authorization issue