# Authorization Exception in only Chrome and Safari when using Elasticsearch 2.3.0

**URL:** <https://discuss.elastic.co/t/authorization-exception-in-only-chrome-and-safari-when-using-elasticsearch-2-3-0/46087>\
**Category:** Kibana\
**Created:** [April 1, 2016, 5:00pm UTC](https://discuss.elastic.co/t/authorization-exception-in-only-chrome-and-safari-when-using-elasticsearch-2-3-0/46087 "2016-04-01T17:00:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Court](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/court/32/6640_2.png) [@Court](https://discuss.elastic.co/u/Court)\
**Post date:** [April 1, 2016, 5:00pm UTC](https://discuss.elastic.co/t/authorization-exception-in-only-chrome-and-safari-when-using-elasticsearch-2-3-0/46087/1 "2016-04-01T17:00:21Z")

</div>

If you just upgraded to Elasticsearch 2.3.0 and are now getting fatal "Authorization Exception" errors when you try to access Kibana in Chrome or Safari, you can likely fix the issue with a quick configuration change.

If you have `http.cors.enabled` set in your elasticsearch configuration for Kibana's sake, remove it. This configuration is no longer necessary in Kibana 4.

If you require `http.cors.enabled` in your elasticsearch config for some other reason, then as of ES 2.3.0, you must also set `http.cors.allow-origin`: [https://www.elastic.co/guide/en/elasticsearch/reference/2.3/breaking\_20\_setting\_changes.html#\_cors\_allowed\_origins](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/breaking_20_setting_changes.html#_cors_allowed_origins)

The github issue for this is [https://github.com/elastic/kibana/issues/6719](https://github.com/elastic/kibana/issues/6719)

---

<div class="post-metadata">

**Author:** ![Court](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/court/32/6640_2.png) [@Court](https://discuss.elastic.co/u/Court)\
**Post date:** [April 1, 2016, 5:04pm UTC](https://discuss.elastic.co/t/authorization-exception-in-only-chrome-and-safari-when-using-elasticsearch-2-3-0/46087/2 "2016-04-01T17:04:27Z")

</div>

I should note: if you don't have `http.cors.enabled` in your elasticsearch config and are still getting authorization errors, then you are almost certainly encountering a different issue entirely. I recommend posting a separate thread in that case rather than replying to this one.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:57pm UTC](https://discuss.elastic.co/t/authorization-exception-in-only-chrome-and-safari-when-using-elasticsearch-2-3-0/46087/3 "2017-07-06T13:57:11Z")

</div>