Default behavior of xpack.security.enabled


(Tim Mundt) #1

After upgrading an elasticsearch 2 instance to 5.6.9 I got an error "missing authentication token for REST request". I fixed that by setting "xpack.security.enabled: false".

However, I'm also sucessfully running an elasticsearch 5.3 cluster where I didn't need that setting and still can perform any request without authentication.

Has the default behavior of "xpack.security.enabled" changed in one of the last releases or am I missing something else here?


(Tim Vernum) #2

The default behaviour for security is dependent on the license type.

I suspect your 5.3 cluster has a Basic license, nd the 5.6.9 cluster has a trial or gold/platinum license


(Tim Mundt) #3

With both I'm simply using the docker image, no extra license (guess that means "Basic").


(system) #4

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