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

Search Guard configuration GUI enabled when is not #461

Closed
fbacchella opened this Issue Mar 16, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@fbacchella

fbacchella commented Mar 16, 2018

i'm using Search Guard community edition, and disabled entreprise in the elasticsearch.yaml:

searchguard.enterprise_modules_enabled: false

I installed then the kibana plugin and tried to access the configuration gui, as I saw in kibana's log:

log   [14:52:05.591] [info][status][plugin:searchguard@6.2.2] Status changed from yellow to yellow - Search Guard configuration GUI enabled

I think it should have said it's disabled, like other entreprise features:

log   [14:52:05.451] [info][status][plugin:searchguard@6.2.2] Status changed from yellow to yellow - Search Guard multitenancy disabled
log   [14:52:05.452] [info][status][plugin:searchguard@6.2.2] Status changed from yellow to yellow - Search Guard copy JWT params disabled
@jochenkressin

This comment has been minimized.

Show comment
Hide comment
@jochenkressin

jochenkressin Mar 22, 2018

Collaborator

That's not possible technically. During startup of Kibana the ES cluster is not reachable and thus we can't check if the REST API is available on ES or not. The message just states that the Kibana GUI part has been initialized successfully.

However, we will make the log message a bit more obvious, just need to think about the right wording here. Any suggestions?

Collaborator

jochenkressin commented Mar 22, 2018

That's not possible technically. During startup of Kibana the ES cluster is not reachable and thus we can't check if the REST API is available on ES or not. The message just states that the Kibana GUI part has been initialized successfully.

However, we will make the log message a bit more obvious, just need to think about the right wording here. Any suggestions?

@jochenkressin

This comment has been minimized.

Show comment
Hide comment
@jochenkressin

jochenkressin Mar 27, 2018

Collaborator

Will be added in the next release.

Collaborator

jochenkressin commented Mar 27, 2018

Will be added in the next release.

@jochenkressin

This comment has been minimized.

Show comment
Hide comment
@jochenkressin

jochenkressin Apr 3, 2018

Collaborator

Fixed with the release of Search Guard v22 / Kibana Plugin v11 : https://docs.search-guard.com/latest/changelog-6-x-22

Collaborator

jochenkressin commented Apr 3, 2018

Fixed with the release of Search Guard v22 / Kibana Plugin v11 : https://docs.search-guard.com/latest/changelog-6-x-22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment