Currently the search operations in some REST resources will only accept a single keyword as a search filter. This is also forced by the fact that the CLI and the UI provide only a single argument or field to specify the keyword.
The server will use the keyword to search a predefined list of attributes, but the client will not have any control of that. For example, a keyword may be translated into the following LDAP filters:
This behavior needs to be defined properly, and documented too, to make sure the client understands why he/she is getting certain results.
If there are requirements for the keyword itself (e.g. minimum length) it has to be defined & documented too.
It's also possible to make this configurable to allow customization.
Per CS/DS Meeting on 3/24/2014 - confirmed with edewata.
In meeting on 4/9/2014, it was determined that for 10.2 purposes, searches would only be against the following LDAP attributes:
It was also determined that to support searching, we should establish a minimum number of characters for keywords (length of 3 characters surrounded by '*' wildcards).
Additionally, filter customization issues will be addressed in 10.3.
Here are the TPS resources with the proposed attributes to be made searchable with a keyword:
http://pki.fedoraproject.org/wiki/TPS_Database
Moved to 10.2 (May) as this ticket will be closed soon:
edewata wrote: I have fixed the search filters for TPS resources in patch #478 (needs ACK), but there are other resources used in TPS (i.e. users, groups, group members) that are shared with other subsystems. I'm in the middle of working on it, but the changes could affect other subsystems. I need to discuss this with someone. If we don't need to change them we can close the ticket soon. But if we need to change them, I will need more time to test the effects on other subsystems.
New proposed milestone: 10.2 (May)
master:
Configurable search filter will be implemented separately in ticket #988.
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2 - 05/14 (May)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1487
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.