Provide JMX monitoring options to monitor any LDAP related Failures

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: User Management - LDAP
    • None
    • 0
    • 1

      Issue Summary

      When Bitbucket encounters an LDAP-related error, the Bitbucket SYS_AMDIN can identify the problem only by checking the application logs. Providing an easier way to monitor LDAP failures through JMX can be helpful.

      The below exception is thrown in the atlassian-bitbucket.log file:

      2024-04-11 14:51:03,492 WARN [http-nio-7990-exec-13] *JI0HJ2x891x1136168x2 10.10.10.10 "GET /rest/api/1.0/repos HTTP/1.1" c.a.s.i.s.s.PluginAuthenticationProvider ldap_user: Authentication system failed
com.atlassian.bitbucket.auth.AuthenticationSystemException: The remote authentication server is not available. Please try again later.
...
Caused by: com.atlassian.crowd.exception.runtime.CommunicationException: null
...
Caused by: org.springframework.ldap.CommunicationException: ldap-server:3268; nested exception is javax.naming.CommunicationException: ldap-server:3268 [Root exception is java.net.UnknownHostException: ldap-server]

      Workaround

      Monitor the atlassian-bitbucket.log for LDAP errors.

              Assignee:
              Unassigned
              Reporter:
              Danny Samuel
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: