# Unable to login to Kibana **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [January 17, 2020, 5:09am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410 "2020-01-17T05:09:02Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![noble](https://avatars.discourse-cdn.com/v4/letter/n/e19b73/32.png) [@noble](https://discuss.elastic.co/u/noble)\ **Post date:** [January 17, 2020, 5:09am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/1 "2020-01-17T05:09:02Z")
Trying to setup ES with LDAP. Getting the follow error while logging in Kibana. {"statusCode":401,"error":"Unauthorized","message":"[security\_exception] unable to authenticate user [\*\*\*\*\*] for REST request [/\_security/\_authenticate], with { header={ WWW-Authenticate={ 0="Bearer realm=\"security\"" & 1="ApiKey" & 2="Basic realm=\"security\" charset=\"UTF-8\"" } } }"} ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [January 17, 2020, 3:25pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/2 "2020-01-17T15:25:27Z")
There is not enough info in your message for us to help you. What is your configuration ? What error are there in the logs ? ---
**Author:** ![noble](https://avatars.discourse-cdn.com/v4/letter/n/e19b73/32.png) [@noble](https://discuss.elastic.co/u/noble)\ **Post date:** [January 20, 2020, 12:42am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/3 "2020-01-20T00:42:17Z")
Sorry for the late reply. Please find the below details. I tried using AD and the same error persists. **/var/elasticsearch/mycluster.log** [2020-01-20T11:19:54,127][DEBUG][o.e.x.s.a.l.ActiveDirectorySessionFactory] [node-3] Resolved 143 LDAP groups \*\*\*\*\*\*\*Lists all the LDAP groups it found \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* [2020-01-20T11:19:54,128][DEBUG][o.e.x.s.a.l.ActiveDirectorySessionFactory] [node-3] Resolved 0 meta-data fields [{}] for user [CN=admuser,OU=Some OU1,OU=Some OU2,OU=Some OU3OU=SomeOU4,DC=SomeDC,DC=com] [2020-01-20T11:20:18,476][DEBUG][o.e.x.s.a.l.LdapRealm] [node-3] realm [myad] authenticated user [admuser], with roles [[BB\_Server\_Admins]] **/etc/elasticsearch/elasticsearch.yml** xpack: security: authc: realms: active\_directory: myad: order: 0 domain\_name: [domain.com](http://domain.com) url: ldap://SOMEServer.Domain.COM:389 bind\_dn: "CN=some\, user, OU=SomeOU,OU=SomeOU2,OU=SomeOU3,OU=SomeOU4,OU=SomeOU5,DC=SomeDC,DC=com" follow\_referrals: false **Role Mapping.** PUT /\_security/role\_mapping/BB\_Server\_Admins { "roles" : ["BB\_Server\_Admins"], "rules" : { "field" : { "groups" : "CN=BB Server Admins,OU=Groups,OU=SomeOU,OU=SomeOU,OU1=SomeOU2,OU=SomeOU3,DC=SomeDC,DC=com" } }, "enabled": true } _**Roles (created in GUI)**_ { "BB\_Server\_Admins" : { "cluster" : [ "all" ], "indices" : [ { "names" : [ "wazuh-monitoring-3.x-_", "apm-_", "wazuh-alerts-3.x-_" ], "privileges" : [ "all" ], "allow\_restricted\_indices" : false } ], "applications" : [ { "application" : "kibana-.kibana", "privileges" : [ "all" ], "resources" : [ "_" ] } ], "run\_as" : , "metadata" : { }, "transient\_metadata" : { "enabled" : true } } } **ERROR while logging in kibana** {"statusCode":401,"error":"Unauthorized","message":"[security\_exception] unable to authenticate user [admuser] for REST request [/\_security/\_authenticate], with { header={ WWW-Authenticate={ 0="Bearer realm=\"security\"" & 1="ApiKey" & 2="Basic realm=\"security\" charset=\"UTF-8\"" } } }"} ---
**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\ **Post date:** [January 20, 2020, 7:16am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/4 "2020-01-20T07:16:03Z")
Your log file indicates that authentication worked, but you're showing an error from Kibana that shows that it failed. Can you explain the mismatch there? What triggered that successful authentication in the logs, and where is the log from the Kibana failure? ---
**Author:** ![noble](https://avatars.discourse-cdn.com/v4/letter/n/e19b73/32.png) [@noble](https://discuss.elastic.co/u/noble)\ **Post date:** [January 21, 2020, 12:09am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/5 "2020-01-21T00:09:35Z")
Hello Tim, Please find below Kibana logs. Kibana logs where going to stdout by default. So changed it to /var/log/kibana/somfile.log in /etc/kibana/kibana.yml **{"type":"response","@timestamp":"2020-01-20T23:47:15Z","tags":[],"pid":30484,"method":"post","statusCode":204,"r eq":{"url":"/api/security/v1/login","method":"post","headers":{"host":"10.0.0.0:5601","connection":"keep-aliv e","content-length":"62","accept":"application/json, text/plain, _/_","kbn-version":"7.3.0","user-agent":"Mozill a/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36"," content-type":"application/json;charset=UTF-8","origin":"[https://10.0.0.0:5601](https://10.0.0.0:5601)","sec-fetch-site":"same-origin ","sec-fetch-mode":"cors","referer":"[https://10.0.0.0:5601/login","accept-encoding":"gzip](https://10.0.0.0:5601/login%22,%22accept-encoding%22:%22gzip), deflate, br","acce pt-language":"en-US,en;q=0.9"},"remoteAddress":"10.1.1.1","userAgent":"10.1.1.1","referer":"[https://10.0.0.0:5601/login"},"res":{"statusCode":204,"responseTime":18,"contentLength":9},"message":"POST](https://10.0.0.0:5601/login%22%7D,%22res%22:%7B%22statusCode%22:204,%22responseTime%22:18,%22contentLength%22:9%7D,%22message%22:%22POST) /api/security/v1 /login 204 18ms - 9.0B"}** _10.1.1.1 is DHCP server addrs_ **{"type":"error","@timestamp":"2020-01-20T23:47:16Z","tags":["connection","client","error"],"pid":30484,"level":" error","error":{"message":"140541772941184:error:14094416:SSL routines:ssl3\_read\_bytes:sslv3 alert certificate u nknown:../deps/openssl/openssl/ssl/record/rec\_layer\_s3.c:1407:SSL alert number 46\n","name":"Error","stack":"Err or: 140541772941184:error:14094416:SSL routines:ssl3\_read\_bytes:sslv3 alert certificate unknown:../deps/openssl/ openssl/ssl/record/rec\_layer\_s3.c:1407:SSL alert number 46\n"},"message":"140541772941184:error:14094416:SSL rou tines:ssl3\_read\_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec\_layer\_s3.c:1407:SSL alert number 46\n"}** **{"type":"log","@timestamp":"2020-01-20T23:47:16Z","tags":["info","authentication"],"pid":30484,"message":"Authen tication attempt failed: [security\_exception] unable to authenticate user [admuser] for REST request [/\_se curity/\_authenticate], with { header={ WWW-Authenticate={ 0="Bearer realm=\"security\"" & 1="ApiKey" & 2 ="Basic realm=\"security\" charset=\"UTF-8\"" } } }"}** _Bearer realm=\"security\\This is not my realm_ **{"type":"response","@timestamp":"2020-01-20T23:47:16Z","tags":[],"pid":30484,"method":"get","statusCode":401,"re q":{"url":"/","method":"get","headers":{"host":"10.0.0.0:5601","connection":"keep-alive","upgrade-insecure-re quests":"1","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrom e/79.0.3945.130 Safari/537.36","sec-fetch-user":"?1","accept":"text/html,application/xhtml+xml,application/xml;q =0.9,image/webp,image/apng,_/_;q=0.8,application/signed-exchange;v=b3;q=0.9","sec-fetch-site":"same-origin","sec -fetch-mode":"navigate","referer":"[https://10.0.0.1:5601/login","accept-encoding":"gzip](https://10.0.0.1:5601/login%22,%22accept-encoding%22:%22gzip), deflate, br","accept -language":"en-US,en;q=0.9"},"remoteAddress":"10.1.1.1","userAgent":"10.1.1.1","referer":"[https://10.0.0.0:5601/login"},"res":{"statusCode":401,"responseTime":27,"contentLength":9},"message":"GET](https://10.0.0.0:5601/login%22%7D,%22res%22:%7B%22statusCode%22:401,%22responseTime%22:27,%22contentLength%22:9%7D,%22message%22:%22GET) / 401 27ms - 9.0B"}** **{"type":"response","@timestamp":"2020-01-20T23:47:16Z","tags":[],"pid":30484,"method":"get","statusCode":302,"re q":{"url":"/favicon.ico","method":"get","headers":{"host":"10.0.0.0:5601","connection":"keep-alive","user-age nt":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safar i/537.36","accept":"image/webp,image/apng,image/_,_/\*;q=0.8","sec-fetch-site":"same-origin","sec-fetch-mode":"no -cors","referer":"[https://10.0.0.0:5601/","accept-encoding":"gzip](https://10.0.0.0:5601/%22,%22accept-encoding%22:%22gzip), deflate, br","accept-language":"en-US,en;q =0.9"},"remoteAddress":"10.1.1.1","userAgent":"10.1.1.1","referer":"[https://10.0.0.0:5601/"},"res":{"st](https://10.0.0.0:5601/%22%7D,%22res%22:%7B%22st) atusCode":302,"responseTime":3,"contentLength":9},"message":"GET /favicon.ico 302 3ms - 9.0B"}** **{"type":"response","@timestamp":"2020-01-20T23:47:16Z","tags":[],"pid":30484,"method":"get","statusCode":200,"re q":{"url":"/login?next=%2Ffavicon.ico","method":"get","headers":{"host":"10.0.0.0:5601","connection":"keep-al ive","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0. 3945.130 Safari/537.36","accept":"image/webp,image/apng,image/_,_/\*;q=0.8","sec-fetch-site":"same-origin","sec-f etch-mode":"no-cors","referer":"[https://10.0.0.0:5601/","accept-encoding":"gzip](https://10.0.0.0:5601/%22,%22accept-encoding%22:%22gzip), deflate, br","accept-languag e":"en-US,en;q=0.9"},"remoteAddress":"10.1.1.1","userAgent":"10.1.1.1","referer":"[https://10.0.0.0:5601](https://10.0.0.0:5601) /"},"res":{"statusCode":200,"responseTime":374,"contentLength":9},"message":"GET /login?next=%2Ffavicon.ico 200 374ms - 9.0B"}** ---
**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\ **Post date:** [January 21, 2020, 6:28am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/6 "2020-01-21T06:28:23Z")
> [@noble](#): > > Please find below Kibana logs Sorry, that wasn't what I meant. You showed us two things: - An Elasticsearch log that clearly showed authentication working - A Kibana error message that showed authentication not working You didn't explain how those 2 things were related. You've now given us this Kibana log: ```auto {"type":"log","@timestamp":"2020-01-20T23:47:16Z", "tags":["info","authentication"],"pid":30484, "message":"Authentication attempt failed: [security_exception] unable to authenticate user [admuser] for REST request [/_se curity/_authenticate], with { header={ WWW-Authenticate={ 0="Bearer realm=\"security\"" & 1="ApiKey" & 2 ="Basic realm=\"security\" charset=\"UTF-8\"" } } }"} ``` Can you show us the Elasticsearch log for the same timestamp? ---
**Author:** ![noble](https://avatars.discourse-cdn.com/v4/letter/n/e19b73/32.png) [@noble](https://discuss.elastic.co/u/noble)\ **Post date:** [January 22, 2020, 5:30am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/7 "2020-01-22T05:30:36Z")
Hello Tim, Below are the Kibana and ES logs, when I press the login button in Kibana console. _Note: there is a time difference of 1hr between ES and Kibana logs. I tried to change the timezone in Kibana console but its not reflecting in logs._ **Kibana Log** {"type":"log","@timestamp":"2020-01-22T04:55:23Z","tags":["info","authentication"],"pid":13793,"message":"Authentication attempt fail ed: [security\_exception] unable to authenticate user [admuser] for REST request [/\_security/\_authenticate], with { header={ WWW -Authenticate={ 0="Bearer realm=\"security\"" & 1="ApiKey" & 2="Basic realm=\"security\" charset=\"UTF-8\"" } } }"} **ES log** [2020-01-22T15:55:23,006][DEBUG][o.e.x.s.a.l.LdapRealm] [node-3] realm [myrlm] authenticated user [admuser], with roles [[BB\_Server\_Admins]] **This is what I get when I use elastic user** {"type":"log","@timestamp":"2020-01-22T05:05:06Z","tags":["info","audit","security","saved\_objects\_authorization\_success"],"pid":13793,"username":"elastic","action":"get","types":["config"],"args":{"type":"config","id":"7.3.0","options":{}},"eventType":"saved\_objects\_authorization\_success","message":"elastic authorized to get config"} **My Configuration files are as below** > **Summary** > > ===================== 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](https://www.elastic.co/guide/en/elasticsearch/reference/index.html) > > # > > # ---------------------------------- Cluster ----------------------------------- > > # > > # Use a descriptive name for your cluster: > > # > > cluster.name: my-cluster > > # > > # ------------------------------------ Node ------------------------------------ > > # > > # Use a descriptive name for the node: > > # > > node.name: node-3 > > # > > # 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: /var/lib/elasticsearch > > # > > # Path to log files: > > # > > path.logs: /var/log/elasticsearch > > # > > # ----------------------------------- 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: 10.0.0.3 > > # > > # 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 this node is started: > > # The default list of hosts is ["127.0.0.1", "[::1]"] > > # > > discovery.seed\_hosts: ["10.0.0.1", "10.0.0.2", "10.0.0.3"] > > # > > # Bootstrap the cluster using an initial set of master-eligible nodes: > > # > > cluster.initial\_master\_nodes: > > - 10.0.0.1 > - 10.0.0.2 > - 10.0.0.3 > > # For more information, consult the discovery and cluster formation 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 > xpack.security.enabled: true > > # Transport layer > > xpack.security.transport.ssl.enabled: true > xpack.security.transport.ssl.verification\_mode: certificate > xpack.security.transport.ssl.key: /etc/elasticsearch/certs/elasticsearch-3.key > xpack.security.transport.ssl.certificate: /etc/elasticsearch/certs/elasticsearch-3.crt > xpack.security.transport.ssl.certificate\_authorities: ["/etc/elasticsearch/certs/ca.crt"] > > # HTTP layer > > xpack.security.http.ssl.enabled: true > xpack.security.http.ssl.verification\_mode: certificate > xpack.security.http.ssl.key: /etc/elasticsearch/certs/elasticsearch-3.key > xpack.security.http.ssl.certificate: /etc/elasticsearch/certs/elasticsearch-3.crt > xpack.security.http.ssl.certificate\_authorities: ["/etc/elasticsearch/certs/ca.crt"] > > #AD > > xpack: > security: > authc: > realms: > active\_directory: > myrlm: > order: 0 > domain\_name: [domain.com](http://domain.com) > url: ldap://server.domain.COM:389 > bind\_dn: "CN=Some Account\, BB user,OU=someOU1,OU=someOU2,OU=someOU3,OU=someOU4,OU=someOU5,DC=someDC,DC=com" > follow\_referrals: false > **Summary** > > # Kibana is served by a back end server. This setting specifies the port to use. > > #server.port: 5601 > > # Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values. > > # The default is 'localhost', which usually means remote machines will not be able to connect. > > # To allow connections from remote users, set this parameter to a non-loopback address. > > server.host: "0.0.0.0" > > # Enables you to specify a path to mount Kibana at if you are running behind a proxy. > > # Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath > > # from requests it receives, and to prevent a deprecation warning at startup. > > # This setting cannot end in a slash. > > #server.basePath: "" > > # Specifies whether Kibana should rewrite requests that are prefixed with > > # `server.basePath` or require that they are rewritten by your reverse proxy. > > # This setting was effectively always `false` before Kibana 6.3 and will > > # default to `true` starting in Kibana 7.0. > > #server.rewriteBasePath: false > > # The maximum payload size in bytes for incoming server requests. > > #server.maxPayloadBytes: 1048576 > > # The Kibana server's name. This is used for display purposes. > > server.name: "myname" > > # The URLs of the Elasticsearch instances to use for all your queries. > > elasticsearch.hosts: ["[https://10.0.0.1:9200](https://10.0.0.1:9200)", "[https://10.0.0.2:9200](https://10.0.0.2:9200)", "[https://10.0.0.3:9200](https://10.0.0.3:9200)"] > > # When this setting's value is true Kibana uses the hostname specified in the server.host > > # setting. When the value of this setting is false, Kibana uses the hostname of the host > > # that connects to this Kibana instance. > > #elasticsearch.preserveHost: true > > # Kibana uses an index in Elasticsearch to store saved searches, visualizations and > > # dashboards. Kibana creates a new index if the index doesn't already exist. > > #kibana.index: ".kibana" > > # The default application to load. > > #kibana.defaultAppId: "home" > > # If your Elasticsearch is protected with basic authentication, these settings provide > > # the username and password that the Kibana server uses to perform maintenance on the Kibana > > # index at startup. Your Kibana users still need to authenticate with Elasticsearch, which > > # is proxied through the Kibana server. > > #elasticsearch.username: "kibana" > #elasticsearch.password: "pass" > > # Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively. > > # These settings enable SSL for outgoing requests from the Kibana server to the browser. > > #server.ssl.enabled: false > #server.ssl.certificate: /path/to/your/server.crt > #server.ssl.key: /path/to/your/server.key > > # Optional settings that provide the paths to the PEM-format SSL certificate and key files. > > # These files validate that your Elasticsearch backend uses the same key files. > > #elasticsearch.ssl.certificate: /path/to/your/client.crt > #elasticsearch.ssl.key: /path/to/your/client.key > > # Optional setting that enables you to specify a path to the PEM file for the certificate > > # authority for your Elasticsearch instance. > > #elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"] > > # To disregard the validity of SSL certificates, change this setting's value to 'none'. > > #elasticsearch.ssl.verificationMode: full > > # Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of > > # the elasticsearch.requestTimeout setting. > > #elasticsearch.pingTimeout: 1500 > > # Time in milliseconds to wait for responses from the back end or Elasticsearch. This value > > # must be a positive integer. > > elasticsearch.requestTimeout: 30000 > > # List of Kibana client-side headers to send to Elasticsearch. To send _no_ client-side > > # headers, set this value to (an empty list). > > #elasticsearch.requestHeadersWhitelist: [authorization] > > # Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten > > # by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration. > > #elasticsearch.customHeaders: {} > > # Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable. > > #elasticsearch.shardTimeout: 30000 > > # Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying. > > #elasticsearch.startupTimeout: 5000 > > # Logs queries sent to Elasticsearch. Requires logging.verbose set to true. > > #elasticsearch.logQueries: false > > # Specifies the path where Kibana creates the process ID file. > > #pid.file: /var/run/kibana.pid > > # Enables you specify a file where Kibana stores log output. > > logging.dest: /var/log/kibana/some.log > > # Set the value of this setting to true to suppress all logging output. > > #logging.silent: false > > # Set the value of this setting to true to suppress all logging output other than error messages. > > #logging.quiet: false > > # Set the value of this setting to true to log all events, including system usage information > > # and all requests. > > #logging.verbose: false > > # Set the interval in milliseconds to sample system and process performance > > # metrics. Minimum is 100ms. Defaults to 5000. > > #ops.interval: 5000 > > # Specifies locale to be used for all localizable strings, dates and number formats. > > # Supported languages are the following: English - en , by default , Chinese - zh-CN . > > #i18n.locale: "en" > xpack.security.audit.enabled: true > xpack.security.enabled: true > xpack.security.encryptionKey: "\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*" > > # Elasticsearch from/to Kibana > > elasticsearch.ssl.certificateAuthorities: ["/etc/kibana/certs/ca.crt"] > elasticsearch.ssl.certificate: "/etc/kibana/certs/elasticsearch-3.crt" > elasticsearch.ssl.key: "/etc/kibana/certs/elasticsearch-3.key" > > # Browser from/to Kibana > > server.ssl.enabled: true > server.ssl.certificate: "/etc/kibana/certs/elasticsearch-3.crt" > server.ssl.key: "/etc/kibana/certs/elasticsearch-3.key" > elasticsearch.username: "elastic" > elasticsearch.password: "\*\*\*\*\*\*\*\*\*\*\*\*" ---
**Author:** ![noble](https://avatars.discourse-cdn.com/v4/letter/n/e19b73/32.png) [@noble](https://discuss.elastic.co/u/noble)\ **Post date:** [January 30, 2020, 12:18am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/8 "2020-01-30T00:18:41Z")
Sorry, it was my mistake. We had 3 master nodes and I had done the AD configuration only in one node hoping that it will automatically replicate to other nodes. Configuration file was made the same in all the node and bind user password was provided in all - Kibana is now authenticating properly with AD. Thank you ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 27, 2020, 12:18am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana/215410/9 "2020-02-27T00:18:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.