Stay organized with collections
Save and categorize content based on your preferences.
About Chrome Verified Access
Your network service can use the Verified Access feature in the Google Admin
console to communicate with both the client Chrome device and the Verified
Access API. Doing so gains information about the policy compliance
and (optionally) the identity of the client device from Google. To that end,
a Chrome extension must be running on the device that interacts with the
enterprise.platformKeys extension API, and the network service needs to talk to
the Verified Access API.
How Chrome Verified Access Works
Here’s the suggested implementation:
Suggested implementation.
The Chrome extension contacts the Verified Access API to create a challenge.
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.
The network service contacts the Verified Access API to verify the
challenge-response.
In case of successful verification, the network service grants access to
the device.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-16 UTC."],[[["Chrome Verified Access allows network services to verify device compliance and user identity, facilitating secure access control."],["A Chrome extension and communication with the Verified Access API are essential for leveraging this feature."],["The process involves a challenge-response mechanism between the Chrome extension, network service, and the Verified Access API to confirm device legitimacy before granting access."]]],[]]
