Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Tentang Akses Terverifikasi Chrome
Layanan jaringan Anda dapat menggunakan fitur Akses Terverifikasi di konsol
Google Admin untuk berkomunikasi dengan perangkat Chrome klien dan Verified Access API. Tindakan ini akan mendapatkan informasi tentang kepatuhan terhadap kebijakan dan (opsional) identitas perangkat klien dari Google. Untuk itu, ekstensi Chrome harus berjalan di perangkat yang berinteraksi dengan API ekstensi enterprise.platformKeys, dan layanan jaringan harus berkomunikasi dengan Verified Access API.
Cara Kerja Akses Terverifikasi Chrome
Berikut implementasi yang disarankan:
Penerapan yang disarankan.
Ekstensi Chrome menghubungi Verified Access API untuk membuat tantangan.
Ekstensi Chrome memanggil enterprise.platformKeys API untuk membuat respons tantangan dan mengirimkan permintaan akses ke layanan jaringan, termasuk respons tantangan dalam permintaan.
Layanan jaringan menghubungi Verified Access API untuk memverifikasi
respons tantangan.
Jika verifikasi berhasil, layanan jaringan akan memberikan akses ke
perangkat.
[null,null,["Terakhir diperbarui pada 2025-07-25 UTC."],[[["\u003cp\u003eChrome Verified Access allows network services to verify device compliance and user identity, facilitating secure access control.\u003c/p\u003e\n"],["\u003cp\u003eA Chrome extension and communication with the Verified Access API are essential for leveraging this feature.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves a challenge-response mechanism between the Chrome extension, network service, and the Verified Access API to confirm device legitimacy before granting access.\u003c/p\u003e\n"]]],[],null,["# Chrome Verified Access Overview\n\nAbout Chrome Verified Access\n----------------------------\n\nYour network service can use the Verified Access feature in the Google Admin\nconsole to communicate with both the client Chrome device and the Verified\nAccess API. Doing so gains information about the policy compliance\nand (optionally) the identity of the client device from Google. To that end,\na Chrome extension must be running on the device that interacts with the\nenterprise.platformKeys extension API, and the network service needs to talk to\nthe Verified Access API.\n\nHow Chrome Verified Access Works\n--------------------------------\n\nHere's the suggested implementation:\nSuggested implementation.\n\n\u003cbr /\u003e\n\n1. The Chrome extension contacts the Verified Access API to create a challenge.\n2. The Chrome extension calls the enterprise.platformKeys API to generate a challenge-response and sends the access request to the network service, including the challenge-response in the request.\n3. The network service contacts the Verified Access API to verify the challenge-response.\n4. In case of successful verification, the network service grants access to the device."]]
