Discrepancy between gam audit login and actual audit login reports
See original GitHub issueFull steps to reproduce the issue:
- User suspended via google for suspicious activity
- Find event report in Audit > Login
gam report login event <known-event-type> start <start-date> end <end-date> user <user>
Expected outcome: Trying to programmatically fetch user suspensions so that they can be handled in real-time.
In this test case, the event thrown was account_disabled_hijacked
- https://developers.google.com/admin-sdk/reports/v1/appendix/activity/login#account_disabled_hijacked - actual log verbiage corresponding to event name Account <account> disabled because Google has detected a suspicious activity indicating it might have been compromised
Actual outcome: gam reports no instances of the event, whereas google’s login audit does. I allowed for roughly 5 hours between the event and when I tried to poll, however, even 1 hour time delay makes this fairly impractical, as we have additional processes that need to happen when Google suspends a user.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Chris,
Here are the events from the console:
Here is your query: gam report login event account_disabled_hijacked start 2019-10-11T00:00:00.000Z end 2019-10-11T11:59:59.999Z
Note that your query end 2019-10-11T11:59:59.999Z is before the event 2019-10-11T15:54:53.374Z, i believe you want 23:59:59 not 11:59:59
gam report login event account_disabled_hijacked start 2019-10-11T00:00:00.000Z end 2019-10-11T23:59:59.999Z
Ross
ross.scroggs@gmail.com
Yep, that was it. Sigh. Thanks Ross!