[L'OREAL] durable service credential for the Service API, including SQL Editor DDL

Where we stand: with the API key we read and write data maps and query the OData views, and the full loop has now run live on the AI - POC release — an AI-generated rule written in, read back, compiled to SQL, the ETL build triggered, and the view deployed. Everything beyond the data-map write, however, rides the interactive session token (concento-authtoken), which we measured at 300 seconds of life and which only a person completing SSO + MFA can mint. That single constraint is what separates a working PoC from an unattended service.

3. A durable service credential for the Service API, including SQL Editor DDL.

Our solution is being deployed as a service on Google Cloud, where no interactive browser session exists — so a 300-second, human-minted token rules out any scheduled, unattended, or CI operation.

We need an API key or OAuth client-credentials flow for this surface, with the ability to execute DDL through the SQL Editor (ALTER VIEW) — that is how a backed-up view is restored, and the path is already proven working from our code.