# Issue with Auth0 Lock js file loading After Node 22 Update

**URL:** <https://community.auth0.com/t/issue-with-auth0-lock-js-file-loading-after-node-22-update/183987>\
**Category:** Get Help\
**Tags:** login-prompt-new-experience, login-experience\
**Created:** [March 17, 2025, 2:32pm UTC](https://community.auth0.com/t/issue-with-auth0-lock-js-file-loading-after-node-22-update/183987 "2025-03-17T14:32:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bagul](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bagul/32/73140_2.png) [@bagul](https://community.auth0.com/u/bagul)\
**Post date:** [March 17, 2025, 2:32pm UTC](https://community.auth0.com/t/issue-with-auth0-lock-js-file-loading-after-node-22-update/183987/1 "2025-03-17T14:32:50Z")

</div>

We have integrated our application with Auth0, and previously, validations such as blocked user checks were working correctly. We are using the following Lock file:

`<script src="https://cdn.auth0.com/js/lock/11.16.0/lock.min.js"></script>`

However, after updating to Node.js 22, these validations are no longer working as expected.

Specifically, when a blocked user attempts to log in, it displays a flash message:  
“The user is blocked.”

Now, instead of showing this message, an error is raised on our application side like

“OneLogin::RubySaml::ValidationError in Devise::SamlSessionsController#create  
Issuer of the Assertion not found or multiple.”

Is this need any additional configuration for node 22 working with the auth lock script?

Could any one please assist us in resolving this issue?

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [March 17, 2025, 5:34pm UTC](https://community.auth0.com/t/issue-with-auth0-lock-js-file-loading-after-node-22-update/183987/3 "2025-03-17T17:34:49Z")

</div>

Hi @bagul

From the error message that you have posted, it appears that the certificate that you are using to sign the assertion element might be used for a different response element than the one intended or you might be using the wrong certificate.

I would recommend to use [https://www.samltool.com/](https://www.samltool.com/) or [https://samltool.io/](https://samltool.io/) (which is provided by Auth0) in order to validate the XML file used for your SAML connection. Also, check for any add-ons which might be modifying the output.

Regarding this error, you can check out the following posts as well:

- [OneLogin::RubySaml::ValidationError (Issuer of the Assertion not found or multiple.): · Issue #117 · apokalipto/devise\_saml\_authenticatable · GitHub](https://github.com/apokalipto/devise_saml_authenticatable/issues/117)
- [Class: OneLogin::RubySaml::Response — Documentation for ruby-saml (1.18.0)](https://www.rubydoc.info/gems/ruby-saml/OneLogin/RubySaml/Response)

Otherwise, I would recommend to review the following articles:

- [Troubleshoot SAML Configurations](https://auth0.com/docs/troubleshoot/authentication-issues/troubleshoot-saml-configurations#user-cannot-access-the-application)
- [Troubleshoot SAML Errors](https://auth0.com/docs/troubleshoot/authentication-issues/saml-errors)
- [Sign and Encrypt SAML Requests](https://auth0.com/docs/authenticate/protocols/saml/saml-sso-integrations/sign-and-encrypt-saml-requests#change-the-signing-key-for-saml-responses)
- [Migrate from Node 18 to Node 22](https://auth0.com/docs/troubleshoot/product-lifecycle/deprecations-and-migrations/migrate-nodejs-22)

If you have any other questions, feel free to leave a reply!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 31, 2025, 5:35pm UTC](https://community.auth0.com/t/issue-with-auth0-lock-js-file-loading-after-node-22-update/183987/4 "2025-03-31T17:35:42Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.