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

Spectacularly Annoying: Warning: 299 Elasticsearch-7.15.0-79d65f6e357953a5b3cbcc5e2c7c21073d89aa29 #78500

Open
NetwarSystem opened this issue Sep 30, 2021 · 14 comments
Labels
>bug >docs General docs changes :Security/Security Security issues without another label Team:Docs Meta label for docs team Team:Security Meta label for security team v7.15.3 v9.0.0

Comments

@NetwarSystem
Copy link

NetwarSystem commented Sep 30, 2021

Having recently run apt upgrade on an Ubuntu 20.04 box I see that I've now got Elasticsearch 7.15.0 and it comes with a spectacular misfeature - an endless cascade of Warning: 299 regarding network security settings when accessing Kibana.

"Warning: 299 Elasticsearch-7.15.0-79d65f6e357953a5b3cbcc5e2c7c21073d89aa29"

The URL, which can not simply be selected and accessed from the warning, is this:

https://www.elastic.co/guide/en/elasticsearch/reference/7.15/security-minimal-setup.html

I get that Elasticsearch is just trying to head off trouble for people who might install an unprotected system on an internet accessible machine. My system is very well protected by an outer layer access control and I have zero interest in having to jump through hoops like this. It's the middle of the night, and now I have to do this meaningless stuff, then reach out to a dozen users and explain to them that they're going to have to enter a username and password after they get through Cloudflare Access.

This really needs a configuration option like this:

xpack.security.stfu: immediately

@NetwarSystem NetwarSystem added >bug needs:triage Requires assignment of a team area label labels Sep 30, 2021
@DaveCTurner
Copy link
Contributor

It's unclear what warning you are talking about: every deprecation warning emitted by Elasticsearch v7.15.0 starts with Warning: 299 Elasticsearch-7.15.0-79d65f6e357953a5b3cbcc5e2c7c21073d89aa29. I'm going to guess you mean the message with content Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.15/security-minimal-setup.html to enable security. If so you can suppress this warning by configuring security as per the linked docs, or by explicitly indicating to Elasticsearch that you do not want to use the built-in security features by setting xpack.security.enabled: false.

@DaveCTurner DaveCTurner added the :Security/Security Security issues without another label label Sep 30, 2021
@elasticmachine elasticmachine added the Team:Security Meta label for security team label Sep 30, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@DaveCTurner DaveCTurner removed the needs:triage Requires assignment of a team area label label Sep 30, 2021
@DaveCTurner
Copy link
Contributor

IMO there's some kind of a docs bug here, this new warning is pretty chatty but doesn't get a mention in the release notes and I don't see anything obvious which suggests that setting xpack.security.enabled: false will help users that prefer to implement their own security protections around Elasticsearch rather than using the built-in features.

@DaveCTurner DaveCTurner added the >docs General docs changes label Sep 30, 2021
@elasticmachine elasticmachine added the Team:Docs Meta label for docs team label Sep 30, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

@turnUpTheChill
Copy link

I hit this as well, with a fresh local install via brew, and it does make doing anything quite annoying as the messages flood the screen and clicking each one individually is the only way to get rid of them

Screen Shot 2021-10-05 at 3 16 54 PM

@lockewritesdocs
Copy link
Contributor

The same message also appears at the top of every response in Console. There's no way to dismiss this message unless you explicitly enable security. It's a very good thing to enable security, but not having the ability to dismiss the toast notifications or suppress the warning in responses is not ideal and creates a frustrating UX.

cc: @thomheymann and @bytebilly

image

@lockewritesdocs
Copy link
Contributor

This message was added to Elasticsearch in 7.13 through the changes in #70114. Oddly, the notification issues don't seem to occur in Kibana until 7.15.

@bytebilly
Copy link
Contributor

Thanks for raising this issue. The warning is intentional, the annoying UX clearly is not, and may be due to a mix of changes.

You can disable all security warnings by setting xpack.security.enabled: false in the Elasticsearch configuration file, if this is really what you want to do and deployment is properly protected at some other layer.

We are discussing possible ways to improve the experience, even if the problem will not be there in 8.x where security will be enabled by default for all tiers.

@renzedj
Copy link

renzedj commented Nov 11, 2021

You can disable all security warnings by setting xpack.security.enabled: false in the Elasticsearch configuration file, if this is really what you want to do and deployment is properly protected at some other layer.

I've got xpack.security.enabled: false set, and I'm still getting a similar warning in Kibana in 7.15.0:

image

...this is when I'm trying to view the filebeat-* index pattern in Kibana.

@bytebilly
Copy link
Contributor

Hi @drenze-athene, thanks for reporting that. What you see is not a security-related warning, so it's not disabled by that setting.

Where in Kibana are you getting this message? Is this flooding the UI, or is it just a single instance? Thanks.

@renzedj
Copy link

renzedj commented Nov 11, 2021

This is flooding the UI, every time I attempt to view something in Discover or Dashboard. If there's a way to suppress this for now, I'd be obliged...

@bytebilly
Copy link
Contributor

I'm not sure why accessing filebeat-* imply access to .tasks. They seem two unrelated events. Is that happening with other patterns too?

@renzedj
Copy link

renzedj commented Nov 16, 2021 via email

@lockewritesdocs lockewritesdocs removed the Team:Docs Meta label for docs team label Apr 26, 2022
@mark-vieira mark-vieira added v8.5.0 and removed v8.4.0 labels Jul 27, 2022
@elasticsearchmachine elasticsearchmachine added the Team:Docs Meta label for docs team label Jul 27, 2022
@csoulios csoulios added v8.6.0 and removed v8.5.0 labels Sep 21, 2022
@kingherc kingherc added v8.7.0 and removed v8.6.0 labels Nov 16, 2022
@rjernst rjernst added v8.8.0 and removed v8.7.0 labels Feb 8, 2023
@gmarouli gmarouli added v8.9.0 and removed v8.8.0 labels Apr 26, 2023
@quux00 quux00 added v8.11.0 and removed v8.10.0 labels Aug 16, 2023
@mattc58 mattc58 added v8.12.0 and removed v8.11.0 labels Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug >docs General docs changes :Security/Security Security issues without another label Team:Docs Meta label for docs team Team:Security Meta label for security team v7.15.3 v9.0.0
Projects
None yet
Development

No branches or pull requests