-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
server.xsrf.token in config file prevents startup #5635
Comments
I dropped the 4.1.4 label because the 4.1 line doesn't include any of the kbn-version stuff, so the xsrf token stuff shouldn't be removed. |
jbudz
added a commit
to jbudz/kibana
that referenced
this issue
Dec 10, 2015
jbudz
added a commit
that referenced
this issue
Dec 11, 2015
jbudz
added a commit
that referenced
this issue
Dec 11, 2015
jbudz
added a commit
that referenced
this issue
Dec 11, 2015
jbudz
added a commit
that referenced
this issue
Dec 11, 2015
jbudz
added a commit
that referenced
this issue
Dec 11, 2015
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know we removed this, but some users are still going to have it in there. It doesn't feel right to break the config file on a patch release, we should print a deprecation notice and remove the ability to start in 5.0
The text was updated successfully, but these errors were encountered: