Obsolete
Status Update
Comments
bl...@google.com <bl...@google.com> #2
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
,directory-api ,users-list ,next-page-token ,query-parameter ,org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
ar...@freshworks.com <ar...@freshworks.com> #3
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191635.
sh...@freshworks.com <sh...@freshworks.com> #4
nextPageToken randomly disappear depending on the query.
It's only returned if there is another page.
Also the starts with operator doesn't work on orgDepartment :
Can you open another bug for this.
jp...@google.com <jp...@google.com> #5
It's only returned if there is another page.
If less result than the page size, the nextPageToken doesn't exists instead to be null ?
Can you open another bug for this.
Description
Hi all,
Problem you have encountered:
We are having an application with Client ID and Client Secret, which receives data using webhook by subscribing to events like "ADD" , "UPDATE" AND "DELETE".
We do not face any issues with "UPDATE" and "DELETE" event payloads, but we are facing issues for newly created users and when we are trying to retrieve the user details by passing ID, in the "ADD" event.
We us the following Users Directory API:
When we use this API to retrieve the full user details, we receive empty results.
What you expected to happen: When we are passing the ID of the user to retrieve the full user details, we need the full user details.
Steps to reproduce:
Using an authorised app with Client ID and Secret, register webhooks to listen for the events such as "ADD" , "UPDATE" AND "DELETE".
Add a new user in Google Workplace, the logs for the webhook event will be logged and try to retrieve the user details using the user ID.
Thanks in Advance.