Connect Gemini Enterprise Agent Platform (formerly Vertex AI) to import models into the Model Catalogue and agents into the Agent Catalogue. For general information, see Integrations.
Saidot uses Workload Identity Federation (WIF). No service account key is created and no secret is exchanged. Instead, your Google Cloud project trusts one Saidot service identity from Saidot’s Microsoft Entra tenant, with read-only access. You can revoke that access at any time (see Revoke access below).
Setup takes about 15 minutes in the Google Cloud Console. To complete it, you need the following roles on the target project — these are your own permissions for performing the setup, not permissions granted to Saidot:
-
roles/serviceusage.serviceUsageAdmin— to enable the required APIs (step 1) -
roles/iam.workloadIdentityPoolAdmin— to create the pool and provider -
roles/iam.serviceAccountAdmin— to create the service account -
roles/resourcemanager.projectIamAdmin— to grant roles
Values Saidot provides
These identify our service to your project. All five are public identifiers — none is a secret. Copy them exactly; GCP matches them character for character.
|
Value |
Enter it in |
Our value |
|---|---|---|
|
Issuer URL |
Provider → Issuer (URL) — step 4 |
|
|
Audience |
Provider → Allowed audiences — step 4 |
|
|
Our tenant ID |
Attribute condition — step 5 |
|
|
Our app client ID |
Attribute condition — step 5 |
|
|
Our service principal ID |
Grant access → subject — step 7 |
|
Setup WIF via Google Cloud Console
1. Enable the APIs
Go to APIs & Services → Library and enable each of these by searching for it and clicking Enable:
|
API |
Service name |
|---|---|
|
Identity and Access Management (IAM) API |
|
|
Security Token Service API |
|
|
IAM Service Account Credentials API |
|
|
Agent Platform API (formerly Vertex AI API) |
|
|
Agent Registry API |
|
2. Note your project number
On the Dashboard, the Project info card shows the Project ID and Project number. Copy the Project number. WIF resource paths use the number, not the ID.
3. Create the workload identity pool
Go to IAM & Admin → Workload Identity Federation. If you see a "Get started" splash, click Get started; otherwise click + Create pool.
Screen 1:
-
Name:
saidot-wif-pool -
Description: optional
-
Enabled pool: on
-
Continue
4. Add the provider
Screen 2 of the same wizard:
-
Select a provider: OpenID Connect (OIDC)
-
Provider name / ID:
saidot-wif-provider -
Issuer (URL):
https://sts.windows.net/8e629ce8-fc36-4d79-a21e-e31b789b6d74/, trailing slash included -
Leave "JWK file (JSON)" empty (Google will fetch Microsoft's keys from the discovery document)
-
Audiences: choose Allowed audiences and enter
api://b3e49e39-336b-49c0-9ffb-e15ee74ab62c -
Continue
Warning: Do not select Default audience. It does not match the audience in Saidot's tokens, and the connection will fail.
5. Configure attribute mapping and condition
Screen 3:
Under Attribute mapping, fill in:
|
Google attribute |
OIDC field |
|---|---|
|
|
|
|
|
|
|
|
|
Click Add mapping to get extra rows.
Under Attribute conditions, click Add condition and paste:
assertion.tid == '8e629ce8-fc36-4d79-a21e-e31b789b6d74' && assertion.appid == '9b84990a-516d-4da7-b828-d7ce6ab4fd6b'
Then Save.
Warning: Do not skip the condition. Without it, the provider accepts tokens from any app in any Microsoft Entra tenant. The condition limits access to Saidot's service identity only.
6. Create the service account
Go to IAM & Admin → Service Accounts → + Create service account.
-
Name:
wif-saidot-model-agent-reader -
Create and continue
-
Grant this service account access to project: select role Agent Platform Viewer (
roles/aiplatform.viewer) and Agent Registry API Viewer (roles/agentregistry.viewer) -
Continue → Done
Skip the "Grant users access to this service account" step; you'll do the equivalent in the next step through the WIF page, which is less error-prone.
7. Grant the Azure identity permission to impersonate it
Go back to IAM & Admin → Workload Identity Federation and click into saidot-wif-pool. Click Grant access (top of the page).
In the dialog:
-
Choose Grant access using service account impersonation
-
Service account:
wif-saidot-model-agent-reader@<project-id>.iam.gserviceaccount.com -
Select principals: choose Only identities matching the filter
-
Attribute name:
subject -
Attribute value: paste our service principal ID from the table
-
-
Save
This is the click-through equivalent of granting roles/iam.workloadIdentityUser on the service account. You can verify it landed by opening the service account → Permissions tab, where the principal://... member should now appear.
Connect in Saidot
When you've finished, in Saidot, go to Integrations in your Space, select Connect on Gemini Enterprise Agent Platform, and enter:
|
Field |
Example |
|---|---|
|
Project ID |
|
|
Project number |
|
|
Regions |
|
|
Pool ID |
|
|
Provider ID |
|
|
Service account |
|
Info: Saidot queries only the regions you list. Google Cloud has no global list of models and agents, so add every region you deploy to.
Next: import models and agents – see Integrations.
Revoke access
To stop Saidot reading your project, do one of the following in Google Cloud:
-
Remove the
principal://...member from the service account's Permissions tab, or -
Disable or delete
saidot-wif-providerorsaidot-wif-pool.
Saidot can then no longer get access tokens for your project. There is no key to rotate.