include all reports for same sender [353045212]

Assigned

Feature Request

Status Update

No update yet.

Description

ad...@tryriet.com

created issue #1

Jul 15, 2024 12:35PM

Hello,

I'm currently trying to use the the Alert Center API (https://developers.google.com/admin-sdk/alertcenter/reference/rest/v1beta1/alerts/list?hl=fr) but it looks like notifications raised for "User-reported phishing" alerts are unreliable:

For each message reported as phishing in Gmail I would except to find at least one notification in the alert center mentioning the message. Currently it looks like the first report always go through and creates a new alert but if I report another email afterwards it's likely it doesn't end-up in the Alert Center.
Emails created using Gmail API (https://developers.google.com/gmail/api/reference/rest/v1/users.messages/insert) reported as phishing never create a notification in the alert center.

Is it expected behavior from the Alert Center ?

Thank you.

Comments

bl...@google.com <bl...@google.com> #2Jul 15, 2024 01:25PM

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 15, 2024 02:41PM

Status: Won't Fix (Not Reproducible)

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

ad...@tryriet.com <ad...@tryriet.com> #4Jul 15, 2024 02:55PM

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 15, 2024 04:06PM

Status: Assigned (reopened)

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

jp...@google.com <jp...@google.com> #6Jul 15, 2024 04:07PM

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.

ad...@tryriet.com <ad...@tryriet.com> #7Jul 16, 2024 12:19PM

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."

jp...@google.com <jp...@google.com> #8Jul 16, 2024 06:46PM

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

jp...@google.com <jp...@google.com> #9Jul 22, 2024 03:42PM

As of today this is working as intended where there is no new alert for the same sender. The team is reassessing this behavior, and I'm going to leave this issue open for now.