Pelanggan Apigee dapat menyediakan produk API kepada pelanggan (developer aplikasi) dengan
portal developer. Dokumen ini menjelaskan cara cookie digunakan untuk memberikan pengalaman ini kepada pengguna portal.
Cookie untuk semua pengunjung
JSESSIONID: Nilai acak yang digunakan untuk mengorelasikan permintaan web dengan sesi.
X-Apigee-CSRF2: Digunakan untuk semua pengunjung situs,
tetapi hanya diisi setelah pengguna melakukan autentikasi. Hal ini membantu melindungi
dari pemalsuan permintaan lintas situs.
Cookie tambahan untuk pengguna yang terautentikasi
portalSession: Token sesi JWT yang digunakan untuk mengautentikasi permintaan.
Data ini dihapus saat pengguna logout.
portalRefresh: Token refresh JWT yang digunakan
untuk menghasilkan token sesi baru. Data ini dihapus saat pengguna logout.
Cookie khusus untuk layanan identitas
SSO_JSESSIONID: Digunakan oleh layanan identitas untuk mempertahankan sesi login pengguna dan mempertahankan status selama login.
route: Digunakan untuk mengarahkan pengguna ke instance identitas untuk
sesi mereka.
X-Uaa-Csrf: Digunakan oleh layanan identitas untuk melindungi dari
pemalsuan permintaan lintas situs
Penggunaan reCAPTCHA
reCAPTCHA digunakan oleh layanan identitas untuk melindungi dari pelaku robot,
yang dapat menggunakan cookie tambahan, termasuk domain google.com.
Lihat
dokumentasi reCAPTCHA terkait penggunaan cookie mereka.
Integrasi dengan reCAPTCHA menghasilkan cookie recaptcha-ca-t, yang digunakan untuk
menyediakan integrasi keamanan dan perlindungan terhadap aktor robot.
Cookie yang Tidak Digunakan Lagi
portalDefaultDomain (tidak digunakan lagi): Digunakan untuk portal yang mengaktifkan domain kustom sebelum 18 Februari 2020. Fungsi ini
menentukan domain tujuan pengiriman permintaan, dan sejak saat itu
tidak digunakan lagi. Menonaktifkan dan mengaktifkan kembali domain kustom portal mana pun akan menghapusnya.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis document outlines the various cookies used by Apigee and Apigee hybrid developer portals to manage user sessions, authentication, and security, with a focus on their purpose and attributes.\u003c/p\u003e\n"],["\u003cp\u003eSeveral cookies, including JSESSIONID and X-Apigee-CSRF2, are utilized for all visitors to correlate web requests with sessions and protect against cross-site request forgeries.\u003c/p\u003e\n"],["\u003cp\u003eAuthenticated users have additional cookies like portalSession and portalRefresh, which are JWT tokens used for authentication and token refreshing, respectively, and are cleared upon logout.\u003c/p\u003e\n"],["\u003cp\u003eThe identity service employs cookies such as SSO_JSESSIONID, route, and X-Uaa-Csrf to maintain user login sessions, manage user routing, and prevent cross-site request forgeries.\u003c/p\u003e\n"],["\u003cp\u003ereCAPTCHA integration adds a recaptcha-ca-t cookie to enhance security and protect against robot actors, alongside potential cookies from the google.com domain.\u003c/p\u003e\n"]]],[],null,["# Cookies\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\nBackground\n----------\n\n\nApigee customers can provide API products to customers (app developers) with\na developer portal. This document describes how cookies are used to deliver\nthis experience for portal users.\n| **Note:** Unless otherwise specified, cookies may be assumed to to have at least the following attributes:\n|\nCookies for all visitors\n------------------------\n\n- **JSESSIONID**: A random value that is used to correlate web requests with sessions.\n- **X-Apigee-CSRF2** : Used for all visitors to a site, but is only populated after a user authenticates. It helps to protect against cross-site request forgeries. **Note:** This cookie intentionally sets the `HttpOnly` attribute to `false`, as its only purpose is to be read by the client.\n\nAdditional cookies for authenticated users\n------------------------------------------\n\n- **portalSession**: A JWT session token used to authenticate requests. It is cleared on logout.\n- **portalRefresh**: A JWT refresh token used to generate a new session token. It is cleared on logout.\n\nCookies specific to the identity service\n----------------------------------------\n\n- **SSO_JSESSIONID**: Used by the identity service to maintain a logged in session for the user and to maintain state during login.\n- **route**: Used to route a user to an identity instance for their session.\n- **X-Uaa-Csrf**: Used by the identity service to protect against cross-site request forgeries\n\nUse of reCAPTCHA\n----------------\n\n\nreCAPTCHA is used by the identity service to protect against robot actors,\nwhich may utilize additional cookies, including the google.com domain.\nSee\n[reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies) regarding their use of cookies.\n\n\nThe integration with reCAPTCHA generates the **recaptcha-ca-t** cookie, which is used to\nprovide security integration and protection against robot actors.\n\nDeprecated Cookies\n------------------\n\n- **portalDefaultDomain**(deprecated): Was used for portals where the custom domain was enabled before February 18, 2020. It determined which domain to send requests to, and it has since been deprecated. Disabling and re-enabling the custom domain of any portal will remove it."]]
