Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2946

Improve LDAP logging for LDAP errors

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Fixed
    • 2.5.3
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Errors such as these:

      INFO [directory.ldap.util.DirectoryAttributeRetriever] Unsafe or Blank attribute value for attribute <givenName>: ' '

INFO [directory.ldap.util.DirectoryAttributeRetriever] Unsafe or Blank attribute value for attribute <sn>: ' '.

ERROR [[Catalina].[localhost].[/].[default]] Servlet.service() for servlet default threw exception
java.lang.IllegalArgumentException: Not a valid attribute string value:ou$$@\m/@,improper usage of backslash

      Should have more information, without setting the class to TRACE. Example:

      INFO: Unsafe or Blank attribute value for attribute <givenName>. Context: <cn=usertest,dc=example,dc=com>. Attribute was skipped.

WARN: Not a valid attribute string value <ou$$@\m/@>, improper usage of backslash. Attribute: <sn>. Context: <cn=usertest,dc=example,dc=com>. User was skipped.

      It is important to have a Context, Attribute Name, and Attribute Value in a WARN/ERROR message, so that it's easier for administrators to identify the user/group in LDAP that is causing the issue

      Attachments

        Issue Links

          Discovered while testing

          Suggestion - CWD-2960 Improve error message when 'Test search' fails

          • Under Consideration
          mentioned in

          Wiki Page Loading...

          Activity

            People

              dberrueta Diego Berrueta
              fsim Foo Sim (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: