i have configred my splunk deployment (hosted on AWS instances) to use LDAP authentication over ssl, but whenever i try to login using my ldap credentials, i have to click on the login buttom multiple times to successfully login, when i use my local authentication credentials it works fine. Below is a snippet of my authentication.conf configs (with sensitive info masked)
[My_splunk_strategy_name]
SSLEnabled = 1
anonymous_referrals = 1
bindDN = CN=<service account>,OU=<OU Name 1>,OU=<OU Name 2>,OU=<OU Name 3>,DC=<DC Name 1>,DC=<DC Name 2>
bindDNpassword = my_password
charset = utf8
emailAttribute = mail
groupBaseDN = OU=<OU Name 1>,OU=<OU Name 2>,OU=<OU Name 3>,OU=<OU Name 4>,DC=<DC Name 1>,DC=<DC Name 2>;OU=<Another_OU Name 1>,OU=<Another_OU Name 2>,OU=<Another_OU Name 3>,OU=<Another_OU Name 4>,DC=<DC Name 1>,DC=<DC Name 2>
groupMappingAttribute = dn
groupMemberAttribute = member
groupNameAttribute = cn
host = ldap_hostname
nestedGroups = 0
network_timeout = 29
port = 636
realNameAttribute = cn
sizelimit = 2000
timelimit = 28
userBaseDN = DC=<DC Name 1>,DC=<DC Name 2>
userNameAttribute = samaccountname
pagelimit = -1
i have another splunk instance which is using similar configs and authentication works perfectly there (no need to click multiple times). The differances there are
1. there we use ldap and not ldaps
2. there the groupBaseDN has lesser number of OUs
So i tried on my current setup with LDAP (port 389 instead of 636 and SSLEnabled = 0 ) but still faced the same issue.
Am i missing anything here? any suggestions on how to resolve this issue.
Note: The security groups and NACLs rules are not an issue as i have already verified with AWS support on that.
... View more