-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Low
-
Component/s: Integration - Identity
-
None
-
4
-
Major
Issue Summary
While running below API, it returns different results.
For Example:
https://<cloud_url>/rest/api/3/users/search?maxResults=32&startAt=0
- with maxResults = 32 => 24 active users
- with maxResults = 42 => 25 active users
- with maxResults = 50 => 25 active users
- with maxResults = 100 => 31 active users
- with maxResults = 1000 => 31 active users
Steps to Reproduce
- Execute below API with different Maxresults:
https://<cloud_url>/rest/api/3/users/search?maxResults=32&startAt=0
https://<cloud_url>/rest/api/3/users/search?maxResults=50&startAt=0
https://<cloud_url>/rest/api/3/users/search?maxResults=1000&startAt=0
Expected Results
- with maxResults = 32 => 31 active users
- with maxResults = 42 => 31 active users
- with maxResults = 50 => 31 active users
- with maxResults = 100 => 31 active users
- with maxResults = 1000 => 31 active users
Actual Results
- with maxResults = 32 => 24 active users
- with maxResults = 42 => 25 active users
- with maxResults = 50 => 25 active users
- with maxResults = 100 => 31 active users
- with maxResults = 1000 => 31 active users
Workaround
Please use maxResults value to 1000.
- is resolved by
-
GORDIAN-823 Loading...
- mentioned in
-
Page Loading...
- relates to
-
EVEREST-491 Loading...