Skip to main content
Question

Missing IAP Data Access audit logs when IAP is enabled directly on Cloud Run

  • Nov 19, 2026 4:27 PM UTC
  • 0 replies
  • 1 view

Abok_J

Hello Google Cloud Community,

I am investigating missing IAP Data Access audit logs for a Cloud Run service with IAP enabled directly, without a load balancer.

Access enforcement works correctly. Authorized users can access the application, and unauthorized users receive the IAP access-denied page. However, no user-attributed Data Access audit logs are appearing.

Configuration:

  • Cloud Run second-generation service.

  • Project without a Google organization.

  • IAP enabled directly on Cloud Run.

  • No load balancer or serverless NEG.

  • Unauthenticated access disabled.

  • Only the IAP service agent has the Cloud Run Invoker role.

  • Custom OAuth client with External audience and Testing status.

  • DATA_READ audit logging enabled for iap.googleapis.com before testing.

  • Default logging sinks unchanged, with no relevant exclusions.

  • Logs queried using the AllLogs view of the Default bucket.

  • Querying principal has project Owner permissions.

Tests performed:

  • Several successful authenticated browser sessions.

  • Access denied to an unauthorized Google account.

  • Access denied after temporarily removing an authorized user from the IAP policy.

Access enforcement behaved correctly throughout.

Logging results:

  • Zero Data Access audit log entries, even when checked the following day.

  • IAP Admin Activity entries are present for policy changes.

  • Cloud Run request logs are present but contain no user identity.

My questions are:

  1. Does IAP enabled directly on Cloud Run generate per-user authorization audit logs?

  2. Is DATA_READ for iap.googleapis.com sufficient, or are additional settings required?

  3. Are successful and denied requests logged differently?

  4. Does audit logging behavior differ between direct Cloud Run IAP and load-balancer-based IAP?

  5. Does the absence of a Google organization or the use of a custom OAuth client in Testing status affect logging?

  6. Could session reuse, authorization caching or long-lived WebSocket connections explain the missing records?

  7. Is there a supported way to obtain user-attributed access records without modifying the application or provisioning additional infrastructure?

Any clarification or relevant official documentation would be greatly appreciated.

Thank you.