Status Update
Comments
as...@slammar.com <as...@slammar.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...
bl...@google.com <bl...@google.com> #3
jp...@google.com <jp...@google.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.
as...@slammar.com <as...@slammar.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.
as...@slammar.com <as...@slammar.com> #6
If less result than the page size, the nextPageToken doesn't exists instead to be null ?
For any Google API, always check the truthiness of values as the underlying transport implementation may leak through (sometimes on purpose allowing customers to use gRPC) by a default value in a proto not being filtered/translated correctly.
as...@slammar.com <as...@slammar.com> #7
Understood, it's could be good if you can copy the field description of nextPageToken from
jp...@google.com <jp...@google.com> #8
Please share a sample request.
jp...@google.com <jp...@google.com>
as...@slammar.com <as...@slammar.com> #9
Here's an example using the above mentioned API, from the online API explorerer:
userKey = holly.birch@slammar.com
groupIdFilter = id:03znysh73ubxw3q
Request = curl \
'
--header 'Authorization: Bearer [YOUR_ACCESS_TOKEN]' \
--header 'Accept: application/json' \
--compressed
Response = {
"kind": "admin#reports#activities",
"etag": "\"VW4We-znyJl4io05lE7ys5dwONVfQICXOTqYZHTmIXs/Wh2T2DZ2LXoMNuJ5zitClDHoXkY\""
}
as...@slammar.com <as...@slammar.com> #10
jp...@google.com <jp...@google.com>
as...@darktrace.com <as...@darktrace.com> #11
Just wondering if there was any update or if any further info was needed?
Many thanks!
ak...@google.com <ak...@google.com> #12
Hi, please go through this help centre article -
To filter audit logs by groups, you need to allowlist the groups. The above article provides the details on how to allowlist them. We'll update the
Description
Description
When using the Admin SDK to get Logs/Activities, using the GroupIdFilter removes all results. Using the GroupIdFilter removes all results and doesn't actually filter the resultshttps://developers.google.com/admin-sdk/reports/reference/rest/v1/activities/list .
You receive a HTTP 200 OK message but no information or activities. Without the GroupIdFilter, you get all the results just fine.
Impact
HIGH - We cannot filter for massive amounts of logs/activities.