Got it. This will keep that from happening. If you don't want to reprovision- add a property http.cors.enabled. The display name and the actual property name are different.
-D... On Thu, Oct 6, 2016 at 4:07 PM, nickwallen <[email protected]> wrote: > Github user nickwallen commented on the issue: > > https://github.com/apache/incubator-metron/pull/288 > > I am seeing this on a cluster that I deployed with the mpack from > 'master'. ES is happy and excited to play. When I hit up Kibana I get > this error. > > ``` > Courier Fetch Error: unhandled courier request error: Authorization > Exception > Version: 4.5.1 > Build: 9892 > ``` > > In researching the error, I ran across this on [Github/Kibana]( > https://github.com/elastic/kibana/issues/6719) which refers to the > `http.cors.enabled` setting. I remembered you opening this PR and thought > it might connect. > > Now I'm confused though because in this PR you set a > `http_cors_enabled` variable which uses underlines versus > `http.cors.enabled` which is mentioned in the link above. > > > --- > If your project is set up for it, you can reply to this email and have your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, please > contact infrastructure at [email protected] or file a JIRA ticket > with INFRA. > --- >
