Onboard Chromebooks with certificates using Google Workspace and Google Cloud
In this topic, you will learn how to deploy Portnox™ Cloud certificates to Chromebook (ChromeOS) devices using Google Workspace and Google Cloud.
Before you can deploy Portnox Cloud certificates via Google Workspace and Google Cloud, you must complete the following steps:
-
If you plan to use device-based certificates, make sure your Chromebooks are running ChromeOS 138 or later.
-
Make sure that the Google administrator account that you will use for this configuration has the Shared Device Settings privileges.
-
Make sure your organization has an active Chrome Enterprise Upgrade (or Chrome Education Upgrade) license.
-
Have access to a Google Cloud project – either an existing one or a new one you create for this purpose – and administrative (Owner or equivalent) permissions on it. A billing account must be linked to the project; this does not mean you will be charged, but Google requires it to enable APIs. This process generates a small amount of traffic and stays well within Google’s free monthly usage tier even at high volume.
Download the root CA certificate from Portnox Cloud
In this section, you will download the Portnox™ Cloud root CA certificate from the Cloud portal and convert it to the Base-64 encoded X.509 format using a Windows computer.
You need the root CA certificate so that your managed devices can verify the validity of Cloud RADIUS servers, which have certificates signed by this root CA certificate. If the root CA certificate is not distributed to managed devices, some devices may show a security warning each time that the user connects to networks managed by Portnox Cloud.
openssl x509 -inform der -in input_file.cer -outform pem -out output_file.cer.Optional: Hand over information from the Portnox Cloud team to the Google team
In this section, you will learn what information was collected in previous steps from Portnox Cloud, which is needed to configure Google Workspace and Google Cloud to work with Portnox Cloud.
If different people are responsible for managing Portnox Cloud and Google Cloud/Google Workspace, here is the information you need to hand over:
Configure the Google Cloud project
In this section, you will create or select a Google Cloud project, enable the Chrome Management API, create a Pub/Sub topic, create a service account for Portnox Cloud, and download a key for this service account.
Optional: Hand over information from the Google team to the Portnox Cloud team
In this section, you will learn what information was collected in previous steps from Google Cloud, which is needed to configure Portnox Cloud.
If different people are responsible for managing Portnox Cloud and Google Cloud/Google Workspace, here is the information you need to hand over:
Configure Portnox Cloud
In this section, you will turn on certificate provisioning in your Portnox™ Cloud Google Workspace integration, so that Portnox Cloud receives certificate requests from your Pub/Sub subscription.
Configure Google Admin
In this section, you will create a generic Certificate Authority connection and a certificate provisioning profile in the Google Admin console.
Optional: Turn on Google Verified Access
In this section, you will enable Google Verified Access to let network services cryptographically verify that connecting Chromebooks are genuine and policy-compliant.
Google Verified Access lets a network service cryptographically confirm that a connecting Chromebook is genuine, enrolled, and running an unmodified, policy-compliant version of ChromeOS. Setting it up involves two parts: enabling an API in your Google Cloud project and configuring a policy in Google Admin. The matching option in Portnox Cloud (Enable ChromeOS devices synchronization) is already activated if you followed the Portnox Cloud configuration task earlier in this topic.
Result: Portnox Cloud can now validate Google Verified Access policy attributes against Google Workspace during device authentication for ChromeOS risk assessment policies.
Create a profile for the root CA certificate
In this section, you will create a profile in Google Workspace for the downloaded Portnox™ Cloud root CA certificate.
Result: You created a profile for the Portnox Cloud root CA certificate.

Create a Wi-Fi profile
In this section, you will create a Wi-Fi profile in Google Workspace for Chromebooks managed by Portnox™ Cloud.
Result: You created a Wi-Fi profile for the network managed by Portnox Cloud.

Optional: Disable the legacy Secure SCEP configuration
In this section, you will remove the legacy Secure SCEP profile from Google Workspace, so that Chromebooks stop using the older, poll-based certificate enrollment method before you configure the new process.
Result: Devices in the selected organizational unit will no longer enroll for certificates using the legacy Secure SCEP method.
Optional: Remove the previous configuration with the Google Cloud Certificate Connector
In this section, you will remove the elements of the previous process with the Google Cloud Certificate Connector after you confirm that the process described in this topic works.
Result: Your configuration no longer contains any elements of the previous process.
Test your configuration on a managed Chromebook
In this section, you will test the configuration you created by connecting a Chromebook to the network managed by Portnox™ Cloud.
Result: The Chromebook connects automatically, using the certificate issued by Portnox Cloud through Google Cloud and Google Workspace.
If the Chromebook does not connect, check the following:
-
Open chrome://certificate-manager, click on the Your certificates tab, and confirm a certificate was issued.
-
On the Chromebook, open chrome://policy and check that the cert_profile_id value in the RequiredClientCertificateForUser policy matches the ClientCertRef value in the OpenNetworkConfiguration policy. If they don’t match, select the certificate provisioning profile in the Wi-Fi profile again and save it.
-
In Portnox Cloud, check that the Enable Certificate Provisioning checkbox is activated, and that the subscription ID and the key file come from the same Google Cloud project.
-
Check that the Certificate Authority connection configuration identifier and the Certificate provisioning profile config reference values in Google Admin match exactly.
-
Existing setups with GCCC: Check that the GoogleCloudCertificateConnector service on your Windows server is stopped.
-
If you use both user and device certificates, see this KB entry.






















































