-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Remove deprecated xpack.security.enabled config option #111681
Conversation
8d9d046
to
c9ec68a
Compare
@elastic/kibana-core Thomas started this PR to address #54023 However, there is overlap with your larger issue #89584. To quote that issue:
The Security plugin currently has an explicit config option for |
Feel free to remove it in this PR -- currently I am readying a PR to add deprecations to all affected plugins which don't have one yet, but our PR to do the actual removal of the old configs won't come until a follow-up PR. So if this PR merges in the interim, that should be fine. |
ee269cc
to
ccee01f
Compare
8614e8b
to
a287ed9
Compare
To enable or disable the security plugin, set this option in Elasticsearch instead.
The 21 new integrations are all enterprise_search integrations which wasn't included before because the security plugin was disabled (a dependency of enterprise_search).
a287ed9
to
e8ace45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this is the only Fleet-related change in question. Approving for Fleet codeowner review 🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reporting changes LGTM
This is a partial backport of elastic#111681, so the Kibana security plugin is enabled but Elasticsearch security is still disabled.
…#129857) * Test config settings that are exposed to the browser (#129438) (cherry picked from commit 27ff7d3) # Conflicts: # .github/CODEOWNERS # packages/kbn-config-schema/src/index.ts * Enable security plugin in OSS tests This is a partial backport of #111681, so the Kibana security plugin is enabled but Elasticsearch security is still disabled. * Fix exposed config key tests The exposed config keys are slightly different in the 7.17 branch. * Fix UI Capabilities tests The enterpriseSearch plugin does not have a required dependency on the security plugin in the 7.17 branch, so our bacported assertions for these tests needed to change accordingly.
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13)
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13)
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13)
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13)
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13)
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13)
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13) Co-authored-by: Robbert Hink <[email protected]>
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13) Co-authored-by: Robbert Hink <[email protected]>
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13) Co-authored-by: Robbert Hink <[email protected]>
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13) Co-authored-by: Robbert Hink <[email protected]>
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13) Co-authored-by: Robbert Hink <[email protected]>
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards (cherry picked from commit fe73e13) Co-authored-by: Robbert Hink <[email protected]>
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards
The setting `xpack.security.enabled` [has been removed since 8.0.0](elastic/kibana#111681) so following these instructions will result in errors from the Kibana side. This file needs to be adjusted for versions of 8.0.0 and upwards
Depends on #111706This config option is already deprecated in 7.x.
To enable or disable the security plugin, set this option in Elasticsearch instead.
Closes #54023
Release note
Removes the deprecated "xpack.security.enabled" config option. This should instead be controlled via the similarly named config option in elasticsearch.yml.