Les utilisateurs n'ont pas pu accéder à la console Web Splunk en raison de configurations incorrectes dans le fichier authentication.conf, l'interface est active, mais les utilisateurs ne peuvent pas se connecter.
./splunkd.log.1:07-12-2019 11:02:16.104 -0600 WARN ScopedLDAPConnection - strategy="<strategy_name>" LDAP Server returned warning in search for DN="DC=domain,DC=com". reason="Operations error" ./splunkd.log.1:07-12-2019 11:02:16.217 -0600 WARN ScopedLDAPConnection - strategy="<strategy_name>" LDAP Server returned warning in search for DN="DC=domain,DC=com". reason="Operations error" ./splunkd.log.1:07-12-2019 11:02:26.849 -0600 WARN ScopedLDAPConnection - strategy="<strategy_name>" LDAP Server returned warning in search for DN="DC=domain,DC=com". reason="Timed out" ./splunkd.log.1:07-12-2019 11:02:26.849 -0600 INFO AuthenticationManagerLDAP - Could not find user="user_name" with strategy="<strategy_name>" ./splunkd.log.1:07-12-2019 11:02:26.850 -0600 ERROR UserManagerPro - LDAP Login failed, could not find a valid user="user_name" on any configured servers ./splunkd.log.1:07-12-2019 12:08:03.375 -0600 ERROR AdminHandler:AuthenticationHandler - Failed to get LDAP user="user_name" from any configured servers ./splunkd.log.1:07-12-2019 12:08:35.984 -0600 ERROR AdminHandler:AuthenticationHandler - Failed to get LDAP user="user_name" from any configured servers
WARN ScopedLDAPConnection - strategy="<strategy_name" LDAP Server returned warning in search for DN="DC=domain,DC=com". reason="Operations error"
| Révision | Date de publication | Commentaires |
|---|---|---|
1.0 |
28-Sep-2026
|
Première publication |