SSL expired for https://npm.sap.com

[r_torres]

Hi experts!

Today we notice that a nodejs application started to failed when It tries to install hana-client library using the following configuration:

1. npm config set @sap:registry https://npm.sap.com

2. npm install @sap/hana-client

The error was:

npm ERR! code CERT_HAS_EXPIRED
npm ERR! errno CERT_HAS_EXPIRED
npm ERR! request to https://npm.sap.com/@sap%2fhana-client failed, reason: certificate has expired

We checked trought the browser and get the attached image about the certificate.

Help!

Regards

Rosmar

[former_member740941]

We are also seeing this - it's been failing our builds, which is not great.

[r_torres]

Exactly, It's happening the same with our builds,

I hope SAP fixed soon. For now, we disable the validation of SSL during the build, but isn't a recommended thing, just a workaround in the meantime.

[r_torres]

Thanks Thales

I'm going to check this publish. I didn't read this part of the documentation.

Is like you said.

[vijayakm]

Faced the same issues today with @sap/approuter

Fixed the issue by updating file .npmrc entry to @sap:registry=https://registry.npmjs.org/

[rzozmann]

Having a .npmrc in every module makes the resulting *.mtar complete infrastructure dependent and we cannot longer deploy the same MTAR in different environments using different registry caches (other than npm.sap.com and registry.npm.org).

And we found no way to define a global npmrc with our settings on the affected XSA machines. And without any .npmrc the 'xs deploy' will trigger a node modules download from npm.sap.com!

So in think also that SAP has a task!

[thalesvb · Accepted solution]

Not direcly about your question, but they have announced some time ago that their packages were being pushed to public NPM repo, and @sap/hana-client is there. Being the same package you can install from public repo without issues.

[former_member806315]

good morning today 09 May 2022, the certificate about npm.sap.com is expired

[former_member806315]

see the image