Random expiration for Report API [352077669]

Fixed

Bug

Status Update

No update yet.

Description

pb...@bigid.com

created issue #1

Jul 9, 2024 06:27PM

Hey there.

I am using this API method -> https://developers.google.com/admin-sdk/reports/reference/rest/v1/activities/watch#body.SubscriptionChannel

Worked for two weeks, but since yesterday night, started to failing. I am doing a POST to https://admin.googleapis.com/admin/reports/v1/activity/users/all/applications/drive/watch with the following body:

{
    "address": "<ENDPOINT>",
    "id": "GoogleDriveAudits",
    "type": "web_hook"
}

This is a sample of an answer:

{
  "api_object": {
    "kind": "api#channel",
    "id": "GoogleDriveAudits",
    "resourceId": "<resourceID>",
    "resourceUri": "https://admin.googleapis.com/admin/reports/v1/activity/users/all/applications/drive?alt=json&orgUnitID",
    "expiration": "1720568714000"
  },
  "step_status": {
    "code": 1,
    "message": "",
    "verbose": ""
  },
  "type": "json"
}

Problem: Since I am not adding any expiration date into the request, the response gives me 6 hours from the request, but in fact, since yesterday the "watch" is deleted after x random time, like 10 minutes, 1 hours, 5 minutes, etc. It is not constant.

This specific watch, doesn't allow to renew every minute like the PubSub one allows. Is this a bug?

Comments

bl...@google.com <bl...@google.com> #2Jul 9, 2024 06:31PM

Assigned to jp...@google.com.

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:

jp...@google.com <jp...@google.com> #3Jul 9, 2024 06:49PM

Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191635.

pb...@bigid.com <pb...@bigid.com> #4Jul 9, 2024 07:09PM

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> #5Jul 9, 2024 07:10PM

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.

https://issuetracker.google.com/issues/387258073

pb...@bigid.com <pb...@bigid.com> #6Jul 9, 2024 07:39PM

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.

Message last modified on Jul 9, 2024 07:40PM

ad...@capitalone.com <ad...@capitalone.com> #7Jul 9, 2024 08:14PM

Understood, it's could be good if you can copy the field description of nextPageToken from https://developers.google.com/drive/api/reference/rest/v3/files/list to https://developers.google.com/admin-sdk/directory/reference/rest/v1/groups/list. Because there only "Token used to access next page of this result." and is not clear than "The page token for the next page of files. This will be absent if the end of the files list has been reached."

Message last modified on Jul 9, 2024 08:15PM

jp...@google.com <jp...@google.com> #8Jul 10, 2024 02:46AM

I have reported this to the engineering team and future updates will be shared here. Thank you for your patience.

pb...@bigid.com <pb...@bigid.com> #9Jul 11, 2024 10:49PM

Hey there.

Did you already identify the issue? It seems the Drive API (

https://developers.google.com/drive/api/reference/rest/v3/changes/watch) is not working indeed. This Drive API v3, is not even sending any logs using the watch.

jp...@google.com <jp...@google.com> Jul 12, 2024 03:27PM

Marked as fixed.