入口網站使用者在整合式入口網站完成應用程式註冊程序後，入口網站會將應用程式相關資訊傳送至 Apigee，包括應用程式名稱和與應用程式相關聯的 API 產品。如果 Apigee 成功註冊應用程式，Apigee 會將單一 API 金鑰傳回入口網站。入口網站使用者可透過該 API 金鑰，存取與應用程式相關聯的 API 產品。
應用程式和 API 金鑰的相關資訊只會儲存在 Apigee，不會儲存在入口網站。當入口網站使用者透過入口網站查看應用程式資訊 (例如透過「我的應用程式」頁面)，入口網站會使用 API 金鑰向 Apigee 提出要求，以存取資訊。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[[["\u003cp\u003eApigee provides an integrated portal for managing API access, documenting APIs, and fostering a developer community, with tools to quickly build a developer portal.\u003c/p\u003e\n"],["\u003cp\u003eThe integrated portal offers key features such as customizable look-and-feel, content development with Markdown and HTML, auto-generated API documentation, self-service registration, and advanced customizations.\u003c/p\u003e\n"],["\u003cp\u003eApigee addresses security through built-in features, including HTTPS and TLS enforcement, protection against various attacks like XSS and CSRF, and Google Cloud data encryption and retention policies, although it's not FedRAMP authorized.\u003c/p\u003e\n"],["\u003cp\u003eThe integrated portal communicates with Apigee via HTTP/HTTPS REST requests to store and retrieve information about apps, API keys, and developer account details, with all the data stored on Apigee.\u003c/p\u003e\n"],["\u003cp\u003eThe sample portal offers starter pages like Home, Get Started, APIs, My Apps, Sign In, and Terms and Conditions to kickstart portal development, with features like auto-generated content and customizable styling.\u003c/p\u003e\n"]]],[],null,["# Building your integrated portal\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n\u003cbr /\u003e\n\nApigee delivers a simple-to-use, integrated portal to document and manage access to your APIs,\nand foster your app developer community.\n\nAll users of Apigee have access to the integrated portal development tools enabling them to build their\nown developer portal quickly, providing an alternative to the\n[Drupal-based portal development](/apigee/docs/api-platform/publish/drupal/open-source-drupal-8). For a feature comparison,\nsee [Comparison of developer portal features](/apigee/docs/api-platform/publish/intro-portals#feature-comparison).\n\nKey features and benefits\n-------------------------\n\nThe integrated portal provides you with the following key features and benefits:\n\nHow Apigee addresses security in the integrated portal\n------------------------------------------------------\n\nThe following table describes how Apigee addresses security through built-in features in the integrated portal.\n| **Important** : While Apigee monitors for and addresses newly emerging security features as required, it is important to note that Apigee integrated portals are not [FedRAMP](https://www.fedramp.gov/) authorized.\n\nHow the integrated portal communicates with Apigee\n--------------------------------------------------\n\nA majority of the information used by the developer portal is stored on Apigee. The portal acts as a client to Apigee. As necessary, the developer portal sends an HTTP or HTTPS REST request to retrieve information from or send information to Apigee. For example, when a portal user registers a new app on the portal, the portal sends a request to Apigee to store information about the app.\n| All interactions between the developer portal and Apigee are initiated by the portal. Apigee does not make requests to the portal, it only responds to requests made from the portal.\n\nThe following sections provide more detail.\n\n### Where app registration and API keys are stored\n\nWhen a portal user completes the app registration process on the integrated portal, the portal sends information about the app to Apigee, including the app name and the API products associated with the app. If Apigee registers the app successfully, Apigee returns a single API key to the portal. The portal user uses that API key to access the API products associated with the app.\n\nInformation about the apps and API keys is stored on Apigee only; it is not stored on the portal. When a portal user uses the portal to view information about an app, via the My Apps page for example, the portal makes a request to Apigee with the API key to access the information.\n\nSimilarly, when a portal user adds, removes, or modifies an app, the portal sends the modifications to Apigee to be stored.\n\nBecause all information about apps and API keys is stored on Apigee, an Apigee administrator can modify the information by using the Apigee UI or management API. For example, an administrator can:\n\n- Add, remove, or modify a developer app\n- Approve or revoke an API key for a developer app\n\nFor more information, see [Controlling access to your APIs by registering apps](/apigee/docs/api-platform/publish/creating-apps-surface-your-api).\n\n### Where app developer account information is stored\n\nDeveloper account information is stored on Apigee, as follows:\n\n- Using the [built-in identity provider](/apigee/docs/api-platform/publish/portal/portal-identity-provider#built-in), when a portal user **[creates an account](/apigee/docs/api-platform/publish/portal/portal-interact#register)** , the information is stored in the identity provider and is displayed on the [Users page](/apigee/docs/api-platform/publish/portal/api-portal-users#explore_the_users_page).\n- Using the [SAML identity provider](/apigee/docs/api-platform/publish/portal/portal-identity-provider#saml), when a portal user **[signs in to the portal](/apigee/docs/api-platform/publish/portal/portal-interact#saml-auth)** , a shadow record of the information is stored in the identity provider and is displayed on the [Users page](/apigee/docs/api-platform/publish/portal/api-portal-users#explore_the_users_page).\n- After a portal user [**registers a developer app**](/apigee/docs/api-platform/publish/portal/portal-interact#register-apps), the user account information is synced to and available on Apigee on the [Developers page](/apigee/docs/api-platform/publish/adding-developers-your-api-product#ui).\n\n| Note the following:\n|\n| - Although it is possible to create accounts on behalf of portal users manually using the Apigee UI, as described in [Registering app developers](/apigee/docs/api-platform/publish/adding-developers-your-api-product), this is not recommended to ensure that the user accounts on the integrated portal and Apigee stay in sync.\n| - When you [delete a user](/apigee/docs/api-platform/publish/portal/api-portal-users#delete), the associated app developer is not deleted from the Developers page on Apigee. Similarly, when you [delete a developer](/apigee/docs/api-platform/publish/adding-developers-your-api-product#deletingadeveloper) from Apigee, the user account information is not deleted from the identity provider.\n\nThe following user account information is stored on Apigee:\n\n- First and last name\n- Email address\n- Username\n- Portal account status (active or inactive)\n- Portal role (authenticated user, administrator, other)\n- Role-based permissions\n- Teams to which the portal user is a member (if you have [enrolled in the Preview release of the teams feature](/apigee/docs/api-platform/publish/portal/developer-teams#enroll))\n\nThe email address is the primary key used by Apigee to identify the developer and each must be unique. From the primary key, Apigee generates a unique developer ID for each organization to which the developer belongs.\n\nFor more information, see [Register app developers](/apigee/docs/api-platform/publish/adding-developers-your-api-product).\n\n### Where developer team information is stored (Preview)\n\n| **Note:** You must [enroll in the Preview release of the teams feature](/apigee/docs/api-platform/publish/portal/developer-teams#enroll).\n\nWhen a developer team is created on the portal by a portal user, the developer team information is stored on Apigee, including:\n\n- Developer team name and description\n- Developer team members and their roles\n- Apps to which the developer team is assigned\n- Audiences assigned to the developer team\n- Time the developer team was created\n\nA unique, auto-generated email address is generated for the developer team and serves as the primary key used by Apigee to identify the developer team.\n\nFor more information, see [Share responsibility for an app using developer teams (Preview)](/apigee/docs/api-platform/publish/portal/portal-interact#teams) and [Manage developer teams](/apigee/docs/api-platform/publish/portal/developer-teams).\n\nAbout the sample portal\n-----------------------\n\nWhen you create a new portal, a set of starter pages is provided for you to use as a jump-off point. The starter pages contain demo content to help inspire your own portal development as you replace the text and images with your unique content. The sample portal theme uses [material design theming](https://material.angular.io/guide/theming) and [SCSS](https://sass-lang.com/).\n\nThe following shows the home page of the sample portal.\n\nThe starter pages provided with the sample portal include:"]]
