User search field 'startIndex' limits number of results returned

By: Daniel Chase user 16 Mar 2018 at 9:43 a.m. CDT

6 Responses
Daniel Chase gravatar
The maximum number of results returned by a User query is 200. This is fine since the 'startIndex' parameter presumably allows us to begin our search beyond the first 200 records. However, when using a nonzero startIndex, the search ends up returning (200 - startIndex + 1) results. For instance, If I attempt to begin my 200-item search at index 195, only 6 results are returned. If I attempt to begin my 200-item search at index 201 or later, zero items are returned. I know that there are more than 200 total users in the system because I can delete them individually yet the total number returned stays at 200. Am I leveraging the startIndex parameter incorrectly?
Ubuntu 16.04
closed

Answers

By Thomas Gasmyr Mougang staff 19 Mar 2018 at 8:40 a.m. CDT

Copy
Thomas Gasmyr Mougang gravatar
Hi **Daniel**, > Am I leveraging the start index parameter incorrectly? You are right, thank you for pointing out that problem. The search method is somehow misleading. An issue has been created [here](https://github.com/GluuFederation/SCIM-Client/issues/69) to fix that. As a workaround, you can increase the MAX_COUNT value in OxTrust AdminUI. Steps to follow: 1. Login into Gluu server admin 1. Navigate to `Configuration` > `JSON configuration` 1. Select `OxTrust Configuration` tab 1. Scroll at the bottom of the page 1. Increase the value of `MAX COUNT` under `Scim properties`

By Thomas Gasmyr Mougang staff 20 Mar 2018 at 1:20 a.m. CDT

Copy
Thomas Gasmyr Mougang gravatar
Hi **Daniel**, Still need assistance?

By Daniel Chase user 20 Mar 2018 at 7:55 a.m. CDT

Copy
Daniel Chase gravatar
Thanks... no, I just didn't realize I needed to close out the ticket. Thank you for following up.

By Daniel Chase user 13 Jun 2018 at 3:37 p.m. CDT

Copy
Daniel Chase gravatar
Hi Thomas, I was just wondering when we might be able to anticipate a fix for this issue? Because there is (to my knowledge) no way to access the LDAP entries programmatically apart from using SCIM, we are not able to audit our gluu profile entries until this issue is resolved. The suggested workaround is not feasible in our case, as increasing the MAX value to accommodate our number of users (700k) caused the server to crash. Thank you, Dan

By Thomas Gasmyr Mougang staff 18 Jun 2018 at 12:56 a.m. CDT

Copy
Thomas Gasmyr Mougang gravatar
Probably in version **3.1.4**.

By Jose Gonzalez staff 17 Jul 2018 at 8:46 a.m. CDT

Copy
Jose Gonzalez gravatar
Hi @all, The [issue fix](https://github.com/GluuFederation/SCIM-Client/issues/69) will be available in **3.1.4** (ETA is Sept 4th).

Post an answer