• 6
    • 1
    • 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.

      Issue Summary

      Customer reports that when searching for users in Audit Log, the query is case sensitive. So, varying cases in usernames, displays name and e-mails may cause them not to be found. The same applies for groups.

      Environment

      Reproduced on

      • Crowd 3.6 and 3.7
      • Postgres

      Steps to Reproduce

      1. Sample user name: Guest
      2. Access Crowd, got to Audit Logs
      3. In User filter, type 'guest'
      4. Delete the field content and type 'Guest'
      5. Delete the field content and type 'GUEST'

      Expected Results

      Find the user typed in either lower, upper or mixed cases

      Actual Results

      User can only be found if the username it is typed exactly as stored.

      The query it performs in Postgres use comparison operation LIKE instead of ILIKE.

      Excerpt from Postgres log:

      [64807]: [565-1] user=postgres,db=crowd_360,app=PostgreSQL JDBC Driver,client=127.0.0.1 LOG:  execute <unnamed>: select distinct entities1_.entity_name as col_0_0_, entities1_.entity_id as col_1_0_, entities1_.entity_type as col_2_0_ from cwd_audit_log_changeset auditlogch0_ inner join cwd_audit_log_entity entities1_ on auditlogch0_.id=entities1_.changeset_id where entities1_.entity_type=$1 and (entities1_.entity_name like $2) order by col_0_0_ ASC limit $3
      [64807]: [566-1] user=postgres,db=crowd_360,app=PostgreSQL JDBC Driver,client=127.0.0.1 DETAIL:  parameters: $1 = 'USER', $2 = 'Test%', $3 = '11'
      

      Workaround

      None at the moment. User name has to be typed in exact casing as it is stored.

            [CWD-5480] Searching in Audit Log is Case Sensitive

              Unassigned Unassigned
              eviana Edson (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: