Comment 1 for bug 1079661

Moved this bug to keystone because it's the controllers that are defaulting to 30 results per page, but we haven't actually exposed paging to the API yet. Either the default paging needs to be removed, or the API implementation and client need to be updated to support paging.

This is spec'd in identity-api v3 for all collections as:

  "links": {
      "previous": url,
      "self": url,
      "next": url,
  }

Where next/previous could be null if you're at either limit of the pagination.