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

Jump to bottom

Better error messages when some nodes don't have security enabled #36230

Open
nik9000 opened this issue Dec 4, 2018 · 2 comments
Open

Better error messages when some nodes don't have security enabled #36230

nik9000 opened this issue Dec 4, 2018 · 2 comments
Labels
:Security/Security Security issues without another label Team:Security Meta label for security team

Comments

@nik9000
Copy link
Member

nik9000 commented Dec 4, 2018

Right now if you configure security and don't set xpack.license.self_generated.type to trial then configure security it is quite possible to end up with a cluster that won't fully form. The master nodes will come up, and, when minimum_master_nodes of them have shown up, they'll self generate a basic license. This basic license will cause security to disable itself and then other nodes that connect to it won't join the cluster because the master doesn't send an authentication token.
@nik9000 nik9000 added the :Security/Security Security issues without another label label Dec 4, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@tvernum
Copy link
Contributor

tvernum commented May 22, 2019

Relates: #42153

@rjernst rjernst added the Team:Security Meta label for security team label May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Security/Security Security issues without another label Team:Security Meta label for security team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nik9000 @rjernst @tvernum @elasticmachine