We are currently testing changes to the CIS Person API that modify the behavior of the
/v2/users/id/all API route. This route currently returns list of user identifiers, however, it is not paginated.
While this worked fine so far, our next update of CIS will support far more users (almost 100, 000) and therefore this endpoint requires pagination as the response would otherwise be too large to handle. Unfortunately, it cannot work without pagination which means it’s a breaking change if you’re currently using it.
The few users of this route will be contacted (granted we have your contact information) directly as well.
Does this affect me?
- If you are not using
/v2/users/id/allyou can disregard this message and you are not affected.
- If you do not know what CIS API is, or do not use it, you are not affected.
It affects me, what should I do
- Please contact us (here or on Slack #iam if you have Slack access)
- Add code to handle the pagination if you receive an error. You the pagination works the same way as the user profile retrieval pagination, and the pagination key is provided through the
nextPagefield. Here is an example: https://github.com/mozilla-iam/cis/blob/master/python-modules/cis_publisher/cis_publisher/publisher.py#L285-L313