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://www.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?
Hi Team, Any update on this or anything we can try to identify the authorization issue
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
Thanks for the follow up. i have 2 follow up questions
1. is the token in the nprmc file and the variable group where we are creating token same ? in that case why we need to mention in 2 places ?
2. how does infragistics pick up the nprmc file. that file is part of project. do we need to place in some directory or it will be automatically read
I have been looking into your question and regarding the first one, I could say that both approaches mentioned in our topic are equivalent and there is no need to set the token in both places. Depending on your requirements and scenario, you could store the token either in the source code i.e. in the local .npmrc file, or in azure as it is described in this section of our documentation.
Regarding the second question - the .npmrc file is for npm. Its purpose is when 'npm install' is executed to provide information where to look for the `@infragistics/` package and the auth details to our registry endpoint. It could be provided globally, in your project, etc. More about it could be found here.
If you require any further assistance on the matter or if the issue still persists, please let me know.
Hey thanks foe the update
we have tried 2 things
1. with Access token usage using nprmc. in this case we have given registry, auth token , username which is my email etc asper the format and nprmc file and we got 401
2. Tried azure pipe line configuration and removed nprmc file. in this case we are getting 404 error as it is not connecting to the private repo. need some help to trouble shoot same
Hello,As I mentioned in my initial response error 401 means that you do not have access to the packages due to a lack of ‘_auth’ section or wrong token at the .npmrc file. So, did you have the chance to verify that everything is correct i.e. the token is valid and in the .npmrc you are not setting ‘auth’ instead of ‘_auth’?
Also, you can try login to our ProGet site, and check whether you see iginteui-angular package under the js-licensed feed here.
Regarding the 404 error, please let me know whether you are setting https://packages.infragistics.com/npm/js-licensed/ as @infragistics:registry.
In addition, I have created a private case with an ID C-00226301 for you and will continue sending updates through it.
Yes we are able to access pro site and we have responded to your email with data requested