# Auth0.min.js version 9.15.0 does not support CORS

**URL:** <https://community.auth0.com/t/auth0-min-js-version-9-15-0-does-not-support-cors/60867>\
**Category:** Get Help\
**Tags:** cors, auth0\
**Created:** [April 10, 2021, 12:47am UTC](https://community.auth0.com/t/auth0-min-js-version-9-15-0-does-not-support-cors/60867 "2021-04-10T00:47:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paton](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/paton/32/12364_2.png) [@Paton](https://community.auth0.com/u/Paton)\
**Post date:** [April 10, 2021, 12:47am UTC](https://community.auth0.com/t/auth0-min-js-version-9-15-0-does-not-support-cors/60867/1 "2021-04-10T00:47:41Z")

</div>

The latest deployed release of auth0.min.js (version 9.15.0) does not support CORS and therefore third-party subresource integrity hash generators cannot be used.

[https://cdn.auth0.com/js/auth0/9.15.0/auth0.min.js](https://cdn.auth0.com/js/auth0/9.15.0/auth0.min.js) does not work with [https://www.srihash.org/](https://www.srihash.org/) and the SRI generator claims it’s because the URL does not support CORS.

All prior versions of auth0.min.js worked just fine with third-party SRI hash generators, so something is different about the way this latest release was deployed.

Please fix this!

---

<div class="post-metadata">

**Author:** ![stephanie.chamblee](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/stephanie.chamblee/32/26087_2.png) [@stephanie.chamblee](https://community.auth0.com/u/stephanie.chamblee)\
**Post date:** [April 12, 2021, 11:22am UTC](https://community.auth0.com/t/auth0-min-js-version-9-15-0-does-not-support-cors/60867/3 "2021-04-12T11:22:17Z")

</div>

Hi @Paton,

In order to confirm when the change was introduced, does the CORS issue occur when reverted to the very last version (9.14.3)?

Also, are you using `auth0.js` in an embedded login form or in a customized Universal Login?

Looking at the [repo](https://github.com/auth0/auth0.js), it looks like the changes made in version `9.15.0` were:

- Apply secure flag to cookies when running on https protocol
- Add onRedirecting login hook
- Add support for the new Organizations feature that’s currently in beta

---

<div class="post-metadata">

**Author:** ![harrisonm](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/harrisonm/32/13593_2.png) [@harrisonm](https://community.auth0.com/u/harrisonm)\
**Post date:** [April 13, 2021, 8:50pm UTC](https://community.auth0.com/t/auth0-min-js-version-9-15-0-does-not-support-cors/60867/4 "2021-04-13T20:50:02Z")

</div>

Can confirm that 9.14.3 does not have this problem. 9.15 does not return the required CORS header.

---

<div class="post-metadata">

**Author:** ![Paton](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/paton/32/12364_2.png) [@Paton](https://community.auth0.com/u/Paton)\
**Post date:** [April 19, 2021, 7:01am UTC](https://community.auth0.com/t/auth0-min-js-version-9-15-0-does-not-support-cors/60867/5 "2021-04-19T07:01:53Z")

</div>

You are now sending the right CORS information to permit subresource integrity hash generation. Looks like you fixed the problem with that URL, thanks. Hopefully you also fixed the bug in your deployment tools/config?

---

<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:** [May 4, 2021, 7:02am UTC](https://community.auth0.com/t/auth0-min-js-version-9-15-0-does-not-support-cors/60867/6 "2021-05-04T07:02:41Z")

</div>

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