[OPENAM-16020] Resource set Search in admin UI is case sensitive Created: 12/Mar/20  Updated: 25/Mar/20

Status: Open
Project: OpenAM
Component/s: console, policy
Affects Version/s:
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: William Hepler Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: Console, EDISON, admin, policy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Support Ticket IDs:


Bug description

When comparing the searching for Policy sets and Resource types there are inconsistencies in case sensitivity 

How to reproduce the issue

  1. In the Admin console, under Authorization- Policy Sets search for default
  2. The results will show hits for Default 
  3. In the Admin console, under Authorization- Resource Sets search for resource
  4. The results will only show results for resource, lower case. If you search for Resource you will get no results.
Expected behaviour
Case in-sensitive searches would be preferred 
Current behaviour
Searches for Resource sets are case sensitive 

Work around

None, search resources using both cases for the word

Code analysis

Policy Sets queries: _queryFilter:displayName eq "*default*" AND name eq "^(?!sunAMDelegationService$).*" 
Resource Types queries: _queryFilter:name co "resource" AND name eq "^(?!Delegation Service$).*" 

Comment by Michael Gardner [ 24/Mar/20 ]

The Expected and Current Behaviors are not written to describe the way I believe the system should work.

I want consistent case-INsensitive searches and lists throughout the UI.  The Policy Set search behaves as I expect (case-insensitive); the Resource Types do not.  Please don't "break" the Policy Set search too.

When I have 100+ Resource Types that includes "site xxx" and "Site yyy", I don't want a search for "site" or "Site" to only find one of them, I want that search to find both.

I can think of no good reason for a UI to be case-sensitive in searches and sorting.  Imagine if Google Search worked that way.  Or Amazon.  Etc.  The UI should be case-INsensitive throughout.

Generated at Sat Nov 28 22:03:10 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.