Unable to Login as Active Directory User per Kibana (but API works)

Elastic Stack Kibana
1

Unable to Login as Active Directory User per Kibana,
but Login per curl from kibana node works well, also the role mapping.

How to debug/solve this problem?

KIBANA per WEBINTERFACE:

"error" : {
    "root_cause" : [
      {
        "type" : "security_exception",
        "reason" : "unable to authenticate user [aduser] for REST request [/_security/_authenticate?pretty]",
        "header" : {
          "WWW-Authenticate" : [
            "Bearer realm=\"security\"",
            "ApiKey",
            "Basic realm=\"security\" charset=\"UTF-8\""
          ]
        }
      }
    ],

API per cURL:

root@server: /usr/share/kibana/bin # curl --noproxy "*" -k  -u aduser:password -X GET "https://<elasticsearchnode>:9200/_security/_authenticate?pretty"
{
  "username" : "aduser",
  "roles" : [
    "kibana_admin",
    "superuser"
  ],
  "full_name" : null,
  "email" : null,
  "metadata" : {
    "ldap_dn" : "CN=FirstName LastName,OU=OUUnit,OU=Unit,DC=mydomain,DC=local",
    "ldap_groups" : [
      "CN=Users,CN=Builtin,DC=mydomain,DC=local",
      "CN=Domain Users,CN=Users,DC=mydomain,DC=local",
      "CN=groupname,CN=Users,DC=mydomain,DC=local"
    ]
  },
  "enabled" : true,
  "authentication_realm" : {
    "name" : "my_ad",
    "type" : "active_directory"
  },
  "lookup_realm" : {
    "name" : "my_ad",
    "type" : "active_directory"
  }
}
2

Are you using proxy infront of Kibana? Are there any logs ? what does the web console output say? Typically users do pass the token or auth headers via a reverse proxy. Would that work in your case?more information required.

Thanks
Rashmi

3

we resolved this issue. configuration is correct.

reason was a bad certificate on one cluster member data node.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.