-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get_group_users returns only 1000 elements #73
Comments
You're only getting 1 page of results (see Pagination). For both Postman and Python code, you need to keep retrieving pages by repeatedly grabbing the |
Thank you @nbarbettini, but I know about Pagination.
|
Ah, I gotcha. Sorry about that. This library is not currently being maintained, so you will have to write your own pagination code. You could look at |
TY. I have already solved the problem in this way. This is just a issue to fix in the future. Perhaps I will make a pullrequest if I have time. |
👍 Thanks for reporting! I'll leave this open, although we aren't currently planning any Python work in the near future. |
We have recently released a 1.x version of this SDK and all api calls and setup is different which should resolve this issue. Please check out our new version on PyPi. This new release includes pagination capabilities which should resolve this issue for you. If you find that you are still having an issue, please let us know if you are still having this issue. |
@bretterer Hello! I've got the several problem in SDK ver. 1.6.0 |
@Andrey-Danilenko Yes, 200 is a hard limit and you have to use pagination (it doesn't depend on SDK). How to use pagination with Python SDK - https://github.com/okta/okta-sdk-python#pagination |
users contains only first 1000 items.
After debug:
response = ApiClient.get_path(self, '/{0}/users'.format(gid))
'next' in response.links
returns TrueBased on the description should return 10,000.
https://developer.okta.com/docs/api/resources/groups/#list-group-members
In any case, the case of large groups is not taken into account.
Also checked with postman. The same behavior.
I also suspect that other API methods may have a similar problem.
The text was updated successfully, but these errors were encountered: