Incorrect link for Troubleshooting LDAP Error Codes when testing User Directory

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 4.4.0
    • Affects Version/s: 4.3.2
    • Component/s: None
    • None

      Summary

      When testing the remote directory connection, if an error is encountered, a link is provided to Troubleshooting LDAP Error Codes. This is a dead link that points to https://confluence.atlassian.com/display/BitbucketServer/embedded.crowd.support.troubleshoot

      Steps to Reproduce

      1. Create a new LDAP User Directory
      2. Set the Base DN to a path that is not valid
      3. Click "Save and Test"
      4. Enter any username and password and click Test Settings
      5. The retrieve user test will fail with the following message:

        Test retrieve user : Failed
        org.springframework.ldap.NameNotFoundException: [LDAP: error code 32 - No Such Object]; nested exception is javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'dc=internal,dc=jeff,dc=jeff,dc=local'
        For more information regarding LDAP error codes see Troubleshooting LDAP Error Codes.

      Expected Results

      The Troubleshooting LDAP Error Codes link should point to https://confluence.atlassian.com/display/CROWD/Troubleshooting+LDAP+Error+Codes which mirrors the behavior in JIRA.

      Actual Results

      The Troubleshooting LDAP Error Codes points to a dead link at https://confluence.atlassian.com/display/BitbucketServer/embedded.crowd.support.troubleshoot

            Assignee:
            Jeff Thomas
            Reporter:
            Jeff Thomas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: