개발자 포털에서 사용하는 대부분의 정보는 Apigee에 저장됩니다. 이 포털은 Apigee의 클라이언트 역할을 합니다. 필요한 경우 개발자 포털은 HTTP 또는 HTTPS REST 요청을 보내 Apigee에서 정보를 검색하거나 Apigee로 정보를 전송합니다. 예를 들어 포털 사용자가 포털에 새 앱을 등록하면 포털은 앱에 대한 정보를 저장하도록 Apigee에 요청을 보냅니다.
다음 섹션에서 더 자세히 다룹니다.
앱 등록 및 API 키 저장 위치
포털 사용자가 통합 포털에서 앱 등록 프로세스를 완료하면 포털에서 앱 이름 및 앱과 연결된 API 제품을 포함하여 앱에 대한 정보를 Apigee로 전송합니다. Apigee가 앱을 성공적으로 등록하면 Apigee는 포털에 단일 API 키를 반환합니다. 포털 사용자는 이 API 키를 사용하여 앱과 연결된 API 제품에 액세스합니다.
앱 및 API 키에 대한 정보는 Apigee에만 저장되며 포털에는 저장되지 않습니다. 예를 들어 포털 사용자가 포털을 사용하여 내 앱 페이지를 통해 앱에 대한 정보를 볼 때 포털은 정보에 액세스하기 위해 API 키를 사용하여 Apigee에 요청을 수행합니다.
마찬가지로 포털 사용자가 앱을 추가, 삭제 또는 수정하면 포털에서 Apigee에 수정사항을 전송하여 저장합니다.
앱 및 API 키에 대한 모든 정보가 Apigee에 저장되므로 Apigee 관리자는 Apigee UI 또는 Management API를 사용하여 정보를 수정할 수 있습니다. 예를 들어 관리자는 다음 작업을 수행할 수 있습니다.
새 포털을 만들 때 시작 페이지 모음이 제공되며 이를 시작점으로 사용할 수 있습니다. 시작 페이지에는 텍스트와 이미지를 고유한 콘텐츠로 대체할 때 자체 포털 개발에 도움이 되는 데모 콘텐츠가 포함되어 있습니다. 샘플 포털 테마는 머티리얼 디자인 테마 및 SCSS를 사용합니다.
다음은 샘플 포털의 홈페이지입니다.
샘플 포털과 함께 제공되는 시작 페이지에는 다음이 포함됩니다.
페이지
설명
홈
표시되는 API를 설명하는 포털 홈페이지이며, 포털의 기본 홈페이지 역할을 합니다(index.html). 앵귤러 머티리얼 구성요소 추가에 설명된 대로 앵귤러 머티리얼 구성요소를 사용하는 방법을 보여줍니다.
시작하기
샘플 콘텐츠 페이지 튜토리얼을 단계별로 수행하여 이 페이지를 수정하고 상단 탐색 메뉴에 추가하는 방법을 알아보세요.
[[["이해하기 쉬움","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-08-18(UTC)"],[[["\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:"]]
