Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-33509

Improve JIRA logging level to better report wrong username attribute

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • 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

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Summary:

      When LDAP integration is set using Internal Directory with LDAP Authentication and the wrong attribute is set at the User Name Attribute field (it can be a dummy attribute) the following message is thrown into the atlassian-jira-security.log file:

      2013-06-14 18:16:02,970 http-8090-3 anonymous 1096x345x1 12rcd8y 127.0.0.1 /rest/gadget/1.0/login login : 'user_01' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.
      

      The problem:

      The message in the log can be easily misunderstood and lead the investigation to the wrong path. Also, when the authentication fail, the Current Failed Login Count increases, which reinforce the idea the that the LDAP user was found and the login failed by other reasons.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              tcomasseto Tiago Comasseto
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: