Kibana Authentication not working

[vbrundavanam (ravi)]

Hi,

I am using kibana 6.3.2. I am trying to integrate Kibana with our AD. In that process i have done the below steps.

1. License changed to Trail which gives us to add authentication.
   2.Downloaded X-Pack -6.2.4 and to install it, but it is saying X-Pack is already inbuilt for
   6.3.2 version.
   

I followed the below document.
https://www.elastic.co/guide/en/kibana/6.2/installing-xpack-kb.html

i am not able to get the authentication page. Please help me with that.
Please let me know if anything more information is required.

Thanks,
Ravi Kiran.

[rashmi (kulkarni)]

@Oleg or @Brandon_Kobel can I get some help here?

Thanks
Rashmi

[Brandon_Kobel]

Hey @vbrundavanam, like the error message states, starting in 6.3 x-pack is included in our default distribution. You no longer have to to run kibana-plugin install x-pack.

I'd recommend checking out https://www.elastic.co/guide/en/elastic-stack-overview/current/how-security-works.html. The majority of the work will be in configuring Elasticsearch's security, and then Kibana will begin prompting users to login.

[vbrundavanam (ravi)]

Hi Brandon. Thanks for your response. I followed the document you shared.

I tried to configure LDAP realm as per the document. But where as, i can't find the xpack.security.authc.realms.ldap configuration in elasticsearch.yml file.

Please find my elastcisearch.yml configuration.

# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: x.x.x.x
#
# Set a custom port for HTTP:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes: 
#
# For more information, consult the zen discovery module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true 
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: x.x.x.x
#
# Set a custom port for HTTP:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes: 
#
# For more information, consult the zen discovery module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true

let me know if anything more information required.

Regards,
Ravi Kiran

[Brandon_Kobel]

The example elasticsearch.yml file that ships with Elasticsearch does not enumerate all of the potential settings, only the common ones. You can add any settings you wish to this file. All of the settings specified in the example elasticsearch.yml file are also commented out by default, that's what the # at the start of the line represents. You'll likely need to familiarize yourself with the structure of the YAML file format: https://en.wikipedia.org/wiki/YAML

[vbrundavanam (ravi)]

Hi Brandon,

Thanks for response. I am able to login with built-in users.

Now my next step is to integrate with AD.

Can you please provide sample configuration for that,

Thank you in advance.

Regards,
Ravi Kiran

[Brandon_Kobel]

@vbrundavanam the settings that you need are highly dependent on your environment. https://www.elastic.co/guide/en/elasticsearch/reference/7.3/configuring-ad-realm.html walks you through configuring an AD realm.