Paginating with Single Attribute Filtering in JDBC user stores without providing a count only returns up to 100 results across pages.

[BojithaPiyathilake]

Describe the issue:

When paginating with single attribute filtering in JDBC userstores, without providing a count value, the items per page decreases although there are more records available.

First request; Total results which meet the filtering conditions: 1000. Since a count isn't given, the max pagination size of the server (100) is taken, and 100 items per page are displayed - Intended behavior.

Second request; When startIndex is increased to 50, the items per page is reduced to 51, although there should be 100 as the total results are 1000.

Third request; Items per page keep decreasing when the startIndex value is increased.

Fourth request;

How to reproduce:

1. Use a copy of "wso2is-5.12.0-alpha14-SNAPSHOT"
2. Using POSTMAN send a request with a single filter and a startIndex to a domain using a JDBC userstore.
3. Try subsequent requests with increasing startIndex values.

Expected behavior:

Even through the startIndex value increases, the results per page should be 100 until it reaches the max limit of 1000.

Environment information

• Product Version: wso2is-5.12.0-alpha14
• OS: Ubuntu Linux
• Database: MySQL
• Userstore: JDBC

---

[isharak]

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!