Skip to content
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.

Sign up for GitHub

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

[DOCS] Update security deprecation message in migration guide #82816

Merged
merged 2 commits into from
Jan 20, 2022
Merged

[DOCS] Update security deprecation message in migration guide #82816

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c6ed538
[DOCS] Update security deprecation message in migration guide
Jan 19, 2022
96371a3
Update deprecation description
Jan 20, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 19 additions & 6 deletions docs/reference/migration/migrate_7_14.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,15 +145,28 @@ Discontinue use of the `type` parameter in `geo_bounding_box` queries.

[discrete]
[[implicitly-disabled-security]]
.The default behavior of disabling security on basic and trial licenses is deprecated
.Disabling security on basic and trial licenses by default is deprecated.
[%collapsible]
====
*Details* +
Currently, security features are disabled when operating on a basic or trial
license when `xpack.security.enabled` has not been explicitly set to `true`.
This behavior is now deprecated. In version 8.0.0, security features will be
enabled by default for all licenses, unless explicitly disabled (by setting
`xpack.security.enabled` to `false`).
{es} security features are disabled by default when operating on a basic or
trial license if `xpack.security.enabled` is not set to `true`. In {es} 8.0.0,
security features will be enabled by default for all licenses unless you
explicitly disable security by setting `xpack.security.enabled` to `false`
(not recommended).

Before migrating to {es} 8.0.0, you must explicitly set a value for
`xpack.security.enabled` or {es} will fail to start. If you have already
enabled security features by explicitly setting `xpack.security.enabled` to
`true`, your configuration will be respected in 8.0.0.

Otherwise, on every node in your cluster, enable {es} security features by
setting `xpack.security.enabled` to `true` in `elasticsearch.yml`. You then
configure security for the transport layer on each node, which requires
generating a certificate authority (if you don't have one), creating node
security certificates, and configuring internode communication. Refer to
<<security-basic-setup,set up basic security for the {stack}>> for steps on
configuring security.
====

[[reserved-prefixed-realm-names]]
Expand Down