First Last Prev Next    This bug is not in your last search results.
Bug 54152 - UDM REST API does not support searching using 'userexpiry' property
UDM REST API does not support searching using 'userexpiry' property
Status: CLOSED DUPLICATE of bug 54150
Product: UCS
Classification: Unclassified
Component: UDM - REST API
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Florian Best
Daniel Tröder
:
Depends on: 54150
Blocks:
  Show dependency tree / graph
 
Reported: 2021-11-26 11:21 CET by Daniel Tröder
Modified: 2022-10-07 18:24 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2021-11-26 11:21:27 CET 
+++ This bug was initially created as a clone of Bug #54150 +++

The UDM REST API support searching with both LDAP attributes and UDM properties.
When using the 'userexpiry' property that does not work.

--------------------------------------------------------------------------
root@m31:~# curl -i -X GET "http://HOST/univention/udm/users/user/?filter=userexpiry=2021-11-25" -H  "accept: application/json"
# no user is found
--------------------------------------------------------------------------

The same happens for "?filter=shadowExpire=2021-11-25" and "?filter=userexpiry=18956".

It works however with: "?filter=shadowExpire=18956".

Expected behavior is that the filter "userexpiry=2021-11-25" can be used with the UDM REST API.
Comment 1 Daniel Tröder univentionstaff 2021-11-26 11:23:01 CET 
For Bug 54126 we are implementing a workaround for this (using shadowExpire=18956 instead of userexpiry=2021-11-25).
Comment 2 Florian Best univentionstaff 2021-12-13 12:17:52 CET 
Why do we need a clone for this against the UDM REST API?
It is a pure UDM bug.
Comment 3 Daniel Tröder univentionstaff 2021-12-13 15:01:02 CET 
(In reply to Florian Best from comment #2)
> Why do we need a clone for this against the UDM REST API?
> It is a pure UDM bug.

How would I know if one automatically fixes the other?
Maybe different fixes or different release strategies are required for UDM and UDM REST API.
The bug-split allows to handle it separately.
And to write separate tests.
And to QA it separately.
Comment 4 Florian Best univentionstaff 2022-03-14 13:17:36 CET 
WORKSFORME:
curl "http://Administrator:univention@localhost/univention/udm/users/user/?scope=sub&filter=userexpiry=2035-08-08" -H  "accept: application/json" | python -m json.tool

*** This bug has been marked as a duplicate of bug 54150 ***
First Last Prev Next    This bug is not in your last search results.