In the enumeration mode the queries usually return chunks rather than everything as a one huge result. This is a default configuration with AD.
SSSD should detect if the server supports paging and use paging control to request data in a loop rather than in one big chunk.
http://tools.ietf.org/html/rfc2696
This actually would allow better performance since huge groups will come in chunks and if the loop is built in a way that would allow other processing the client would not slow down processing big result set.
Fields changed
coverity: => owner: somebody => sgallagh priority: critical => blocker upgrade: => 0
status: new => assigned
patch: => 1
Fixed by - 5ed0e9f015a9948530292918dce7b8d46dcd0d6b - b35da26911249aa48052655eef02f16e12930cf9
resolution: => fixed status: assigned => closed
And corrected by 8c7e6e71b435857802f12c8de09d34b052880eb6
Backported to sssd-1-5
ce9f6745de1d52ef1161d0d7b09ba039f383a093
milestone: SSSD 1.6.0 => SSSD 1.5.8 rhbz: =>
rhbz: => 0
Metadata Update from @dpal: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.5.8
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1700
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.