Synthèse
After successful procurement, the customer's administrator links the purchase to their actual Gemini Enterprise app environment: Redirect to Gemini Enterprise: The Discovery Engine Administrator will see a "Go to Gemini Enterprise" option directly on the procured Marketplace listing. Project Verification: Clicking this prompts the administrator to log into the Google Cloud project where their Gemini Enterprise licenses are allocated. Note that the customer must ensure this destination Google
After successful procurement, the customer's administrator links the purchase to their actual Gemini Enterprise app environment: Redirect to Gemini Enterprise: The Discovery Engine Administrator will see a "Go to Gemini Enterprise" option directly on the procured Marketplace listing. Project Verification: Clicking this prompts the administrator to log into the Google Cloud project where their Gemini Enterprise licenses are allocated. Note that the customer must ensure this destination Google Cloud project is actively linked to the specific billing account used during procurement. DCR Handshake: The Discovery Engine Administrator configures the agent within the Gemini Enterprise app. At this point, your Dynamic Client Registration (DCR) logic validates the incoming JWT's Order ID against your Firestore records.
If the IDs match, the secure registration completes successfully. Agent successfully Registered: Agent is now successfully registered in Gemini Enterprise. Discovery Engine Administrator can now decide whom to give access to the agent.
Source originale
docs.cloud.google.com