Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini memberikan ringkasan integrasi aplikasi OAuth di Google Cloud.
Anda dapat menggunakan integrasi aplikasi OAuth untuk mengintegrasikan aplikasi berbasis OAuth dengan Google Cloud. Pengguna gabungan dapat menggunakan penyedia identitas (IdP) mereka untuk login ke aplikasi dan mengakses produk serta data Google Cloudmereka. Integrasi aplikasi OAuth adalah fitur
Workforce Identity Federation.
Untuk menggunakan integrasi aplikasi OAuth, Anda harus membuat penyedia dan kumpulan identitas tenaga kerja terlebih dahulu. Kemudian, Anda dapat mendaftarkan aplikasi berbasis OAuth
menggunakan OAuth 2.0. Aplikasi harus terdaftar di organisasi tempat
kumpulan identitas tenaga kerja dan penyedia Anda dikonfigurasi.
Pendaftaran aplikasi OAuth
Untuk mengonfigurasi aplikasi agar dapat mengakses Google Cloud, Anda mendaftarkan
aplikasi dengan Google Cloud dengan membuat kredensial klien OAuth.
Kredensial berisi rahasia klien. Aplikasi menggunakan token akses
untuk mengakses produk dan data Google Cloud .
Mitigasi dan risiko keamanan kredensial serta klien OAuth
Anda harus mengamankan akses ke IAM API serta client ID dan secret. Jika client ID dan secret bocor, masalah keamanan dapat terjadi. Masalah
ini mencakup:
Peniruan identitas: Pengguna berbahaya dengan client ID dan secret Anda dapat membuat
aplikasi yang menyamar sebagai aplikasi sah Anda. Kemudian, mereka dapat
melakukan hal berikut:
Mendapatkan akses yang tidak sah ke data pengguna dan izin yang berhak diperoleh
aplikasi Anda.
Melakukan tindakan atas nama pengguna, seperti memposting konten, melakukan panggilan API, atau mengubah setelan pengguna.
Melakukan serangan phishing, dengan pengguna berbahaya membuat halaman login palsu
yang menyerupai penyedia OAuth. Halaman tersebut kemudian dapat mengelabui pengguna agar
memasukkan kredensial mereka, yang memberikan kredensial kepada pengguna
jahat yang kemudian dapat mengakses akun mereka.
Kerusakan reputasi: Pelanggaran keamanan dapat merusak reputasi aplikasi dan organisasi Anda, sehingga menyebabkan pengguna kehilangan kepercayaan.
Jika terjadi pelanggaran, untuk mengurangi risiko ini dan risiko lainnya, nilai sifat
pelanggaran dan lakukan hal 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-08-21 UTC."],[[["\u003cp\u003eOAuth application integration enables federated users to sign in to applications and access Google Cloud resources using their existing identity provider.\u003c/p\u003e\n"],["\u003cp\u003eTo utilize OAuth application integration, a workforce identity pool and provider must be created, and applications must be registered using OAuth 2.0 within the configured organization.\u003c/p\u003e\n"],["\u003cp\u003eOAuth application integration functions exclusively with Identity-Aware Proxy for secure access.\u003c/p\u003e\n"],["\u003cp\u003eSecurity is crucial, as compromised client IDs and secrets can lead to impersonation, unauthorized data access, and reputational damage.\u003c/p\u003e\n"],["\u003cp\u003eIn case of a security breach, client secrets should be rotated immediately by creating a new credential, disabling the old one, and then deleting it.\u003c/p\u003e\n"]]],[],null,["# OAuth application integration overview\n\nThis page provides an overview of OAuth application integration in Google Cloud.\n\nYou can use OAuth application integration to integrate your OAuth-based\napplications with Google Cloud. Federated users can use their identity provider\n(IdP) to sign in to the applications and access their Google Cloud\nproducts and data. OAuth application integration is a feature of\nWorkforce Identity Federation.\n\nTo use OAuth application integration, you must first create a workforce\nidentity pool and provider. You can then register the OAuth-based application\nusing OAuth 2.0. Applications must be registered in the organization where your\nworkforce identity pool and provider are configured.\n\n\u003cbr /\u003e\n\n| **Important:** OAuth application integration works only with Identity-Aware Proxy.\n\n\u003cbr /\u003e\n\nOAuth application registration\n------------------------------\n\nTo configure an application to access Google Cloud, you [register](/iam/docs/workforce-manage-oauth-app#create) the\napplication with Google Cloud by creating [OAuth client credentials](https://tools.ietf.org/html/rfc6749#section-4.4).\nThe credential contains a client secret. The application uses the access token\nto access the Google Cloud products and data.\n\nOAuth client and credential security risks and mitigations\n----------------------------------------------------------\n\nYou must secure access to the IAM APIs and the client ID and\nsecret. If the client ID and secret is leaked, security issues can result. These\nissues include the following:\n\n- Impersonation: A malicious user with your client ID and secret can create an\n application that masquerades as your legitimate application. They can then\n do the following:\n\n - Gain unauthorized access to the user data and permissions that your application is entitled to.\n - Perform actions on the user's behalf, such as posting content, making API calls, or modifying user settings.\n - Perform phishing attacks, wherein the malicious user creates a fake login page that resembles the OAuth provider. The page can then trick users into entering their credentials, which gives the credentials to the malicious user who can then access their accounts.\n- Reputational damage: A security breach can harm the reputation of your\n application and organization, causing users to lose trust.\n\nIn the event of a breach, to mitigate these and other risks, assess the nature\nof the breach and do the following:\n\n- Ensure that only trusted users have IAM access to the [OAuth\n client and credential API](/iam/docs/workforce-manage-oauth-app).\n\n- Rotate the client secret immediately, by rotating the client credential, as\n follows:\n\n 1. [Create a new client credential](/iam/docs/workforce-manage-oauth-app#create-credential) for the OAuth client.\n 2. [Disable the old client credential](/iam/docs/workforce-manage-oauth-app#disable-credential).\n 3. [Delete the old client credential](/iam/docs/workforce-manage-oauth-app#delete-credential).\n\nWhat's next\n===========\n\n- Learn how to [Manage OAuth applications](/iam/docs/workforce-manage-oauth-app)."]]
