Kibana login page (Access control)

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Hello there,
I have Elasticsearch (Version 1.30.0) and Kibana (Version 3.2.3) on Rancher. I am trying to enable the login page for security purposes. I have added the x-pack configs in Kibana. Also I tied enabling (pack.security.enabled: true) in both elasticsearch and Kibana, but it wont come up after adding. I also tried elasticsearch.username: "kibana", elasticsearch.password: "kibanapassword" in Kibana.yaml but it seems it doesn't pick it up as if I put random entry still comes up. Can you please let me know what I am missing?

Thanks!

[areyja]

I believe you will have to setup password for system users first. Which then will enforce security on you Kibana login and enable you to configure more user roles etc as well going forward -

Command - "elasticsearch-setup-passwords interactive"
Location - elastic bin directory

Use this link to get started - https://www.elastic.co/guide/en/elastic-stack-overview/current/security-getting-started.html

/a

[Christian_Dahlqvist]

None of thise version of Kibana or Elasticsearch exists, so please have a closer look at exactly what you are using. Without knowing the version it is hard to help with this.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

I have them on Rancher and that is the version it is showing, you can find it in the attachment

Also I think here is the correct version: Elastic Search: Elasticsearch 6.0. Kibana version 7.

[Christian_Dahlqvist]

Elasticsearch and Kibana need to be of the same version. That combination will not work.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Both of them are 6.7.0. Can you please tell me now how to do it? Thanks

[Christian_Dahlqvist]

Security is only part of the free basic license from version 6.8 and 7.1 so 6.7 will not have this. You also need to ensure you are using the default distribution and not the oss one.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

I have them on Rancher, any version (7.1.1 and 7.2.0) that I try fails for Elasticsearch. I can somehow update the Kibana but Elasticsearch fails. any idea please?

[Christian_Dahlqvist]

What is the output if you go to Elasticsearch_node:9200 ? I suspect you are using the OSS distribution.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Yes I am using oss: docker.elastic.co/elasticsearch/elasticsearch-oss:7.1.1.
I tried from Apps, Elasticsearch upgrade didnt work. Below is by upgrading workloads, Elasticsearch-client which failed as well.
In [sysctl] log: vm.max_map_count = 262144 (shows terminated)
in elastic search log: (shows notready)

7/18/2019 1:31:37 PM "at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:249) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:37 PM "at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:555) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:37 PM "at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:37 PM "at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]",

7/18/2019 1:31:37 PM "at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]",

7/18/2019 1:31:37 PM "at java.lang.Thread.run(Thread.java:835) [?:?]"] }

7/18/2019 1:31:41 PM {"type": "server", "timestamp": "2019-07-18T17:31:41,405+0000", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "master not discovered yet: have discovered ; discovery will continue using [10.42.2.10:9300, 10.42.0.13:9300, 10.42.1.23:9300] from hosts providers and [{elasticsearch-client-6d6ffbcc4c-4lt6d}{IBxQXRF5QIqCFi7ftdU9Qg}{OHXriPA5RD6YE0rV6tUXIg}{10.42.1.86}{10.42.1.86:9300}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }

7/18/2019 1:31:47 PM {"type": "server", "timestamp": "2019-07-18T17:31:47,299+0000", "level": "DEBUG", "component": "o.e.a.a.c.h.TransportClusterHealthAction", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "no known master node, scheduling a retry" }

7/18/2019 1:31:47 PM {"type": "server", "timestamp": "2019-07-18T17:31:47,299+0000", "level": "DEBUG", "component": "o.e.a.a.c.h.TransportClusterHealthAction", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "timed out while retrying [cluster:monitor/health] after failure (timeout [30s])" }

7/18/2019 1:31:47 PM {"type": "server", "timestamp": "2019-07-18T17:31:47,300+0000", "level": "WARN", "component": "r.suppressed", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "path: /_cluster/health, params: {}" ,

7/18/2019 1:31:47 PM "stacktrace": ["org.elasticsearch.discovery.MasterNotDiscoveredException: null",

7/18/2019 1:31:47 PM "at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$4.onTimeout(TransportMasterNodeAction.java:259) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:47 PM "at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:322) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:47 PM "at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:249) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:47 PM "at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:555) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:47 PM "at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:47 PM "at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]",

7/18/2019 1:31:47 PM "at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]",

7/18/2019 1:31:47 PM "at java.lang.Thread.run(Thread.java:835) [?:?]"] }

7/18/2019 1:31:51 PM {"type": "server", "timestamp": "2019-07-18T17:31:51,405+0000", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "master not discovered yet: have discovered ; discovery will continue using [10.42.2.10:9300, 10.42.0.13:9300, 10.42.1.23:9300] from hosts providers and [{elasticsearch-client-6d6ffbcc4c-4lt6d}{IBxQXRF5QIqCFi7ftdU9Qg}{OHXriPA5RD6YE0rV6tUXIg}{10.42.1.86}{10.42.1.86:9300}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }

7/18/2019 1:31:57 PM {"type": "server", "timestamp": "2019-07-18T17:31:57,299+0000", "level": "DEBUG", "component": "o.e.a.a.c.h.TransportClusterHealthAction", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "no known master node, scheduling a retry" }

7/18/2019 1:31:57 PM {"type": "server", "timestamp": "2019-07-18T17:31:57,302+0000", "level": "DEBUG", "component": "o.e.a.a.c.h.TransportClusterHealthAction", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "timed out while retrying [cluster:monitor/health] after failure (timeout [30s])" }

7/18/2019 1:31:57 PM {"type": "server", "timestamp": "2019-07-18T17:31:57,302+0000", "level": "WARN", "component": "r.suppressed", "cluster.name": "elasticsearch", "node.name": "elasticsearch-client-6d6ffbcc4c-4lt6d", "message": "path: /_cluster/health, params: {}" ,

7/18/2019 1:31:57 PM "stacktrace": ["org.elasticsearch.discovery.MasterNotDiscoveredException: null",

7/18/2019 1:31:57 PM "at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$4.onTimeout(TransportMasterNodeAction.java:259) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:57 PM "at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:322) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:57 PM "at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:249) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:57 PM "at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:555) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:57 PM "at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) [elasticsearch-7.1.1.jar:7.1.1]",

7/18/2019 1:31:57 PM "at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]",

7/18/2019 1:31:57 PM "at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]",

7/18/2019 1:31:57 PM "at java.lang.Thread.run(Thread.java:835) [?:?]"] }

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Also I tried clonning, this time by passing the appVersion and image.tag. But get below error now:

[Christian_Dahlqvist]

You need to use the default distribution. I do not know Rancher though, so can not give any specific advise there.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Thanks a lot.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Quick question, now I am trying EFK, with version oss:7.2.0. Does this version have the login page enabled? Thanks

[Christian_Dahlqvist]

No, it does not.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Thanks, so these are the versions I am using and they don't have Access login enabled there:
docker.elastic.co/kibana/kibana-oss:7.2.0
docker.elastic.co/elasticsearch/elasticsearch-oss:7.2.0
I was wondering if I can get the licensed version on Rancher (like trial) and try it there? Any idea please? Thanks

[Christian_Dahlqvist]

Anyone can download them from the Elastic website. If you need to get it from Rancher I guess it is up to them. You may have to ask there.

[Rozita_Mirmotalebi_U (Rozita Mirmotalebi (US - ASR))]

Hi Christian,
Thanks a lot for the reply. So, I finally could install Elasticsearch and Kibana (7.2.0) on Rancher. I have the trial version of the Kibana and I am trying to add the xpack.security.enabled: true on Elasticsearch and for some reason after adding this it fails and won't start. Can you please help me if I am missing anything here? Thanks