Skip to main content
Question

malachite auth scope for legacy API

  • July 23, 2026
  • 1 reply
  • 27 views

harshal.thakor
Forum|alt.badge.img+5

I was referring to this doc for migrating legacy API to chronicle API.
https://docs.cloud.google.com/chronicle/docs/administration/migrate-from-legacy-api-to-chronicle-api


Is this belowauthorization scope also needs to be migrated? as above document don’t have it. But ,ost of the ingestion scripts use it for initializing http session for ingesting data in SecOps.

AUTHORIZATION_SCOPES = ["https://www.googleapis.com/auth/malachite-ingestion"]

https://docs.cloud.google.com/chronicle/docs/reference/ingestion-api

1 reply

a_aleinikov
Forum|alt.badge.img+8
  • Bronze 2
  • July 25, 2026

If the script still calls malachiteingestion-pa.googleapis.com, keep the malachite-ingestion scope. Once you migrate it to the new chronicle.googleapis.com ingestion methods, replace that scope with https://www.googleapis.com/auth/chronicle or cloud-platform and ensure the service account has the required Chronicle IAM permissions.