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.

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

Set xpack.security.enabled to true for all licenses #72300

Merged
merged 56 commits into from
Aug 9, 2021

Conversation

jkakavas
Copy link
Member

@jkakavas jkakavas commented Apr 27, 2021

This change sets the default value for xpack.security.enabled to true
for all licenses. As such the value is read directly from the node's
settings and not from XPackLicenseState which doesn't need to
keep track of it depending on license changes any more.

@jkakavas
Copy link
Member Author

jkakavas commented May 5, 2021

@elasticmachine run elasticsearch-ci/packaging-sample-unix

@jkakavas
Copy link
Member Author

jkakavas commented May 6, 2021

@elasticmachine run elasticsearch-ci/packaging-sample-unix

1 similar comment
@jkakavas
Copy link
Member Author

jkakavas commented May 6, 2021

@elasticmachine run elasticsearch-ci/packaging-sample-unix

@jkakavas
Copy link
Member Author

jkakavas commented May 6, 2021

@elasticmachine run elasticsearch-ci/packaging-sample-unix

(not running these in vein waiting for the tests to auto-fix themselves, but rather attempting to get some useful logs from the CI workers :) )

…nents that are only loaded when security _is_ enabled
Copy link
Contributor

@albertzaharovits albertzaharovits left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great effort on this one Ioannis!

Looks like you've almost worked through all the minor points I had in real-time, so I think this is good to merge.

@jkakavas
Copy link
Member Author

jkakavas commented Aug 4, 2021

@elasticmachine run elasticsearch-ci/part-2-fips

Copy link
Contributor

@BigPandaToo BigPandaToo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jkakavas
Copy link
Member Author

jkakavas commented Aug 8, 2021

@albertzaharovits I will merge this as is Monday morning, could you unmute the related Packaging Tests in #76124 ?

@jkakavas jkakavas added the v8.0.0 label Aug 8, 2021
@albertzaharovits
Copy link
Contributor

@jkakavas yes, for sure.

@jkakavas jkakavas merged commit fed790e into elastic:master Aug 9, 2021
jkakavas added a commit to jkakavas/homebrew-tap that referenced this pull request Sep 5, 2021
During installation, we start elasticsearch a couple of times and
check that we can connect to it. Since elastic/elasticsearch#72300
this tests ( and installation for that matter) has been failing
since security is enabled by default and we make requests without
credentials.

This change, as a temporary measure, makes it so that we start
elasticsearch with security explicitly disabled temporarily during
installation so that we can make the necessary connection test
requests without credentials.

In a follow-up, we will adjust the Formula to take advantage of
newly added functionality, set and show the password for the
elastic user during installation (similar to what we do in
elastic/elasticsearch#75144). We can then also use this password
to make the test requests without needing to disable authN.
mgreau pushed a commit to elastic/homebrew-tap that referenced this pull request Sep 7, 2021
* Adjust installation test

During installation, we start elasticsearch a couple of times and
check that we can connect to it. Since elastic/elasticsearch#72300
this tests ( and installation for that matter) has been failing
since security is enabled by default and we make requests without
credentials.

This change, as a temporary measure, makes it so that we start
elasticsearch with security explicitly disabled temporarily during
installation so that we can make the necessary connection test
requests without credentials.

In a follow-up, we will adjust the Formula to take advantage of
newly added functionality, set and show the password for the
elastic user during installation (similar to what we do in
elastic/elasticsearch#75144). We can then also use this password
to make the test requests without needing to disable authN.

* that other test too
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>breaking :Security/License License functionality for commercial features Team:Security Meta label for security team v8.0.0-alpha2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants