Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan cara melakukan autentikasi aplikasi atau workload yang berjalan di lingkungan produksi pada Compute Engine, atau yang diuji secara lokal untuk deployment mendatang ke lingkungan produksi. Anda dapat melakukan hal berikut:
Mengautentikasi beban kerja Anda untuk menggunakan Google API
Mengautentikasi workload Anda ke workload lain melalui mTLS
Mengautentikasi beban kerja Anda untuk menggunakan Google API
Gunakan tabel berikut untuk menentukan metode autentikasi yang akan digunakan
untuk workload Anda.
Tugas
Metode
Mengautentikasi aplikasi atau workload dalam produksi
Memberi otorisasi pada aplikasi dan workload yang memerlukan akses ke resource pengguna akhir
Jika Anda mem-build solusi pengembangan atau administrasi yang
memungkinkan pengguna memberi Anda akses ke resource Google Cloud mereka, dapatkan akses
untuk aplikasi Anda ke resource pengguna menggunakan OAuth 2.0. Untuk petunjuk mendetail, lihat
Menggunakan OAuth 2.0 untuk Aplikasi Server Web.
Dalam permintaan Anda, tentukan cakupan akses yang membatasi akses hanya ke metode dan informasi pengguna yang diperlukan oleh aplikasi Anda.
Untuk daftar lengkap layanan dan cakupan yang diperlukan di Google Cloud,
lihat
Cakupan OAuth 2.0 untuk Google API.
Mengautentikasi workload Anda ke workload lain melalui mTLS
Anda dapat mengautentikasi aplikasi atau workload menggunakan
managed workload identity. Metode autentikasi ini menggunakan akun layanan, kumpulan otoritas sertifikasi (CA), dan identitas workload terkelola.
Identitas beban kerja terkelola memungkinkan Anda mengikat identitas yang diautentikasi dengan kuat ke
beban kerja Compute Engine. Google Cloud menyediakan kredensial X.509
yang dikeluarkan dari Layanan Otoritas Sertifikasi yang dapat
digunakan untuk mengautentikasi beban kerja Anda dengan beban kerja lain secara andal melalui
autentikasi TLS (mTLS) bersama.
Workload Anda menggunakan identitas workload terkelola sebagai
identitasnya saat mengautentikasi ke workload lain menggunakan TLS timbal balik (mTLS),
dan menggunakan akun layanan sebagai identitasnya saat mengakses layanan dan resource
Google Cloud lainnya.
[[["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-03 UTC."],[[["\u003cp\u003eThis document outlines how to authenticate applications or workloads in production on Compute Engine or during local testing for future deployment.\u003c/p\u003e\n"],["\u003cp\u003eWorkloads running on Google Cloud VMs in production should use the attached service account for authentication to access Google APIs.\u003c/p\u003e\n"],["\u003cp\u003eWorkloads in development can utilize the Google Cloud SDK and Application Default Credentials for authentication, and for access to end-user resources, they can leverage OAuth 2.0.\u003c/p\u003e\n"],["\u003cp\u003eManaged workload identities are available for strongly attesting identities to Compute Engine workloads, using X.509 credentials for mutual TLS (mTLS) authentication between workloads.\u003c/p\u003e\n"],["\u003cp\u003eManaged workload identities can authenticate to other workloads using mTLS, while the service account provides authentication to other Google Cloud services.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nThis document describes how you authenticate applications or\nworkloads that are either running in a production environment on\nCompute Engine, or being tested locally for future deployment to the\nproduction environment. You can do the following:\n\n- Authenticate your workloads to use Google APIs\n- Authenticate your workloads to other workloads over mTLS\n\nAuthenticate your workloads to use Google APIs\n\nUse the following table to determine which authentication method to use\nfor your workloads.\n\n| **Task** | **Method** |\n|-----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Authenticate apps or workloads that are in production | Use the service account that is attached to the VM. \u003cbr /\u003e This is the most common method for authenticating apps and workloads that are running on virtual machine (VM) instances on Google Cloud. For detailed instructions, see [Authenticate workloads to Google Cloud APIs using service accounts](/compute/docs/access/authenticate-workloads). |\n| Authenticate apps or workloads that are in development | Use Google Cloud SDK and Application Default Credentials. For more information, see [Set up ADC for a local development environment](/docs/authentication/set-up-adc-local-dev-environment). |\n| Authorizing apps and workloads that need access to end-user resources | If you are building development or administration tools where users grant you access to their Google Cloud resources, get your application access to user resources by using OAuth 2.0. For detailed instructions, see [Using OAuth 2.0 for Web Server Applications](https://developers.google.com/identity/protocols/oauth2/web-server). \u003cbr /\u003e In your request, specify an access scope that limits your access to only the methods and user information that your application requires. For a full list of services and required scopes across Google Cloud, see [OAuth 2.0 Scopes for Google APIs](https://developers.google.com/identity/protocols/oauth2/scopes). |\n\nAuthenticate your workloads to other workloads over mTLS\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the\n| General Service Terms section of the\n| [Service Specific Terms](/terms/service-terms#1).\n| Pre-GA features are available \"as is\" and might have limited support. For more\n| information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n|\n| For information about access to this release, see the\n| [access request page](https://forms.gle/KC1Lq77gMn3kTtWDA).\n\nYou can authenticate applications or workloads using\n[managed workload identities](/iam/docs/managed-workload-identity). This\nauthentication method uses a service account, certificate authority (CA) pools,\nand managed workload identities.\n\nManaged workload identities let you bind strongly attested identities to\nyour Compute Engine workloads. Google Cloud provisions X.509 credentials\nissued from the [Certificate Authority Service](/certificate-authority-service) that can\nbe used to reliably authenticate your workload with other workloads over\n[mutual TLS (mTLS)](/chrome-enterprise-premium/docs/understand-mtls)\nauthentication.\n\nYour workload uses the managed workload identity as its\nidentity when it authenticates to other workloads using mutual TLS (mTLS),\nand uses the service account as its identity when it accesses other\nGoogle Cloud services and resources.\n\nFor more information, see\n[Authenticate workloads to other workloads over mTLS](/compute/docs/access/authenticate-workloads-over-mtls).\n\nWhat's next\n\n- Learn more about the following concepts:\n - [Authenticate to Compute Engine](/compute/docs/authentication)\n - [Authentication methods at Google](/docs/authentication)\n - [Managed workload identities](/iam/docs/managed-workload-identity)"]]
