--- title: "POP Setup" slug: "google-apigee-pop-setup" updated: 2026-11-15T16:53:37Z published: 2026-11-15T16:53:37Z canonical: "docs.plainid.io/google-apigee-pop-setup" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.plainid.io/llms.txt > Use this file to discover all available pages before exploring further. # POP Setup PlainID supports an Apigee Policy Orchestration Point (POP) in the Integrations Workspace. The POP receives the traffic that the Authorizer's MCP discovery and Insights capabilities report from Google Apigee, and lists the MCP servers and tools the Platform discovers there. Set up the POP before configuring Apigee. Creating the POP issues the client certificate that Apigee uses to authenticate its reports to the collector. ## Prerequisites The following are required: - The Google Cloud project ID and the name of the Apigee API proxy that reports to PlainID. - A Google Cloud service account with the **Apigee Read-only Admin** role (`roles/apigee.readOnlyAdmin`), and a JSON key for it. The Platform uses this account to read Apigee proxies and deployments, and never changes the Apigee configuration. For the steps, see [Service accounts](https://cloud.google.com/iam/docs/service-accounts) and [Create and delete service account keys](https://cloud.google.com/iam/docs/keys-create-delete) in the Google Cloud documentation. - An existing Application and a Policies Workspace in the PlainID Environment. ## Creating the POP **To create the POP:** 1. In the Integrations Workspace, create a new POP and select **Apigee**. See [Managing POPs](https://docs.plainid.io/docs/managing-pops) for more information. 2. Enter the connection details described in the table below. 3. Link an existing Application and a Policies Workspace. The Platform selects the Agent Registry as the linked Identities Workspace automatically. 4. Save the POP. 5. The **Certificate download** window opens and lists the files to download. Select **Download** to save the certificate files, then select **Done**. ### Connection Details | Field | Description | | --- | --- | | **GCP Project ID** | The Google Cloud project that contains the Apigee organization. | | **Proxy Name** | The name of the Apigee API proxy that reports to PlainID. | | **Service Account Key** | The JSON key file of the service account. Upload the file or paste its contents. | The **Service Account Key** can be changed after the POP is created. All other fields are fixed at creation. ## Working with the Certificate The POP issues a client certificate that Apigee presents each time it reports traffic. The certificate is valid for **one year** from the day the POP is created. The download includes two PEM files: the certificate and its private key. ### Adding the Certificate to Apigee The certificate goes into the `plainid-collector` TLS keystore in the Apigee Environment, with one alias for each proxy that reports to PlainID. Each alias must meet these requirements: - **Alias name:** the API proxy name, exactly as it appears in Apigee, for example `plainid-mcp-proxy`. - **Type:** key and certificate. - **Files:** the certificate file and the key file from the POP download. - **Key password:** none. For the steps, see the keystores and truststores section of the Apigee documentation. See [Configuring the Apigee Authorizer](https://docs.plainid.io/docs/apigee-installation) for the rest of the Environment configuration. ### Getting a New Certificate A new certificate can be downloaded for an existing POP at any time. **To get a new certificate:** 1. In the Integrations Workspace, click on the three dots next on the Apigee POP card. 2. Select **Download Certificate**. The Platform generates a new certificate and downloads it. 3. In the `plainid-collector` keystore, upload the new certificate and key to each proxy's alias. ## Viewing Discovered Objects After Apigee starts reporting, open the POP to see what the Platform discovered: - **Observability** opens by default and shows the traffic Apigee reports. - **Vendor Objects** lists the MCP servers and tools the Platform discovered through Apigee. ## Notes - The Platform discovers only MCP servers and traffic from proxies that call the `plainid-mcp-bundle` or `plainid-insights-discoverer` Shared Flow. See [Configuring the Apigee Authorizer](https://docs.plainid.io/docs/apigee-installation) to add them. - If a proxy has no matching alias in the `plainid-collector` keystore, PlainID doesn't receive its records, and Apigee shows no error. - Treat the certificate and key files as secrets. They authenticate Apigee to the Platform. - Treat the service account key as a secret. Don't store it in a code repository.