SAML (Security Assertion Markup Language) adalah standar terbuka yang
memungkinkan penyedia identitas meneruskan kredensial otorisasi ke penyedia layanan. Dengan menggunakan SAML dengan Apigee, Anda dapat mendukung SSO untuk UI Apigee.
Cara kerja SAML dengan Apigee
Spesifikasi SAML menentukan tiga entitas:
Principal (pengguna UI Apigee)
Penyedia layanan (Google Cloud Platform)
Penyedia identitas (penyedia pihak ketiga mana pun yang mendukung SAML 2.0)
Saat SAML diaktifkan, akun utama (pengguna UI Apigee) meminta akses ke penyedia layanan
(Google Cloud Platform). Google Cloud Platform (dalam perannya sebagai penyedia layanan SAML) kemudian meminta dan mendapatkan
pernyataan identitas dari penyedia identitas SAML pihak ketiga dan menggunakan pernyataan tersebut untuk membuat token OAuth 2.0
yang diperlukan untuk mengakses UI Apigee. Pengguna kemudian dialihkan ke UI Apigee.
Keuntungan autentikasi SAML
Autentikasi SAML menawarkan beberapa keuntungan. Dengan menggunakan SAML, Anda dapat:
Mengambil kontrol penuh atas pengelolaan pengguna: Hubungkan server SAML perusahaan Anda ke Apigee. Saat pengguna keluar dari organisasi Anda
dan aksesnya dihentikan secara terpusat, mereka akan otomatis ditolak aksesnya ke Apigee.
Mengontrol cara pengguna melakukan autentikasi untuk mengakses Apigee: Pilih berbagai jenis autentikasi untuk organisasi Apigee Anda.
Mengontrol kebijakan autentikasi: Penyedia SAML Anda mungkin mendukung
kebijakan autentikasi yang lebih sesuai dengan standar perusahaan Anda.
Pantau login, logout, upaya login yang gagal, dan aktivitas berisiko tinggi
di deployment Apigee Anda.
Menggunakan SAML dengan Apigee
Untuk menggunakan SAML dengan Apigee, lihat referensi yang disediakan dalam tabel berikut.
[[["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-05 UTC."],[[["\u003cp\u003eSAML enables single sign-on (SSO) for the Apigee UI by allowing a third-party identity provider to pass authorization credentials to Google Cloud Platform, acting as the service provider.\u003c/p\u003e\n"],["\u003cp\u003eWhen enabled, SAML authentication allows the Apigee UI user to be redirected via Google Cloud Platform to access the platform.\u003c/p\u003e\n"],["\u003cp\u003eUtilizing SAML with Apigee grants control over user management, authentication methods, and authentication policies, including the monitoring of logins and high-risk activities.\u003c/p\u003e\n"],["\u003cp\u003eSAML is exclusively for authenticating users into the Apigee UI, while authorization within Apigee is still managed through Apigee user roles.\u003c/p\u003e\n"],["\u003cp\u003eThis only applies to Apigee and does not apply to Apigee hybrid.\u003c/p\u003e\n"]]],[],null,["# SAML overview\n\n*This page\napplies to **Apigee** , but not to **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nSAML (Security Assertion Markup Language) is an open standard that\nallows an identity provider to pass authorization credentials to a service provider. By using SAML with Apigee, you can support SSO\nfor the Apigee UI.\n\nHow SAML works with Apigee\n--------------------------\n\nThe SAML specification defines three entities:\n\n- Principal (Apigee UI user)\n- Service provider (Google Cloud Platform)\n- Identity provider (any third-party provider that supports SAML 2.0)\n\nWhen SAML is enabled, the principal (an Apigee UI user) requests access to the service provider\n(Google Cloud Platform). Google Cloud Platform (in its role as a SAML service provider) then requests and obtains an\nidentity assertion from the third-party SAML identity provider and uses that assertion to create the OAuth 2.0\ntoken required to access the Apigee UI. The user is then redirected to the Apigee UI.\n\nAdvantages of SAML authentication\n---------------------------------\n\nSAML authentication offers several advantages. By using SAML you can:\n\n- **Take full control of user management:** Connect your company's SAML server to Apigee. When users leave your organization and are deprovisioned centrally, they are automatically denied access to Apigee.\n- **Control how users authenticate to access Apigee:** Select different authentication types for your Apigee organizations.\n- **Control authentication policies:** Your SAML provider may support authentication policies that are more in line with your enterprise standards.\n- **Monitor logins, logouts, unsuccessful login attempts and high risk activities** on your Apigee deployment.\n\n| **Note** : SAML is only used for authentication by the Apigee UI. Authorization is still controlled by Apigee user roles. See [Apigee roles](/apigee/docs/api-platform/system-administration/apigee-roles) for more.\n\nUsing SAML with Apigee\n----------------------\n\n\nTo use SAML with Apigee, refer to the resources provided in the following table."]]
