When calling json/sessions/?_queryID=all with lots of sessions already created, only the 120 of them are returned.
This is because each Server responding to the Session Request uses its configured limit to determine how many SessionInfo's are returned.
Importantly the solution must be able to scale to whatever size we plan to deploy OpenAM to. This could mean many thousands or millions of active users and thereforeSessions.
The current proposal would be to improve the type of information that can be specifiedin the SessionRequest query. This would allow the caller to define how much informationto return in the query.
This would allow us to make use of the ForgeRock REST functionality for paging to thenallow the SessionResource to control which page of SessionInfo should be returned from which server.
This is a stories worth of work rather than a simple bug fix.