LogoLogo
LogoLogo
  • Welcome
  • Details
  • Editions
  • Use Cases
  • SCEPMAN Deployment
    • Getting Started
      • Standard Guide
      • Extended Guide
    • Permissions
      • Azure App Registration
      • Managed Identities
    • Deployment Options
      • Marketplace deployment
      • Enterprise deployment
      • Terraform deployment
    • Root CA
    • Intermediate CA
  • Certificate Management
    • Revocation
    • Microsoft Intune
      • Windows
        • Certificate Based Authentication for RDP
      • macOS
      • Android
      • iOS/iPadOS
      • Linux
    • Jamf Pro
      • General Configuration
      • Computers
      • Devices
      • Users
    • Other MDM Solutions
      • Google Workspace
        • ChromeOS
      • Kandji
      • Mosyle
      • SOTI MobiControl
    • Certificate Master
      • Manage Certificates
      • Certificate Signing Request (CSR)
      • TLS Server Certificate
      • Sub CA Certificate
      • Code Signing Certificate
      • Client Certificate
      • User Certificate
    • Domain Controller Certificates
    • Enrollment REST API
      • Self Service Enrollment
        • Intune Managed Linux Client
        • Unmanaged Linux Client
      • API Enrollment
        • Linux Server
        • Windows Server
      • SCEPmanClient
  • Azure Configuration
    • Application Insights
    • App Service Sizing
      • Autoscaling
    • Custom Domain
    • Geo-Redundancy
    • Health Check
      • Using 3rd Party Monitoring
    • Log Management
    • Moving Resources
    • Private Endpoints
    • Split-Tenancy
  • Update Strategy
  • SCEPman Configuration
    • SCEPman Settings
      • Basics
      • Certificates
      • Certificate Master
      • CRL
      • Dependencies (Azure Services)
        • Azure KeyVault
        • Logging
        • Microsoft Entra ID (Azure AD)
        • National Cloud Platforms
      • Enrollment REST API
      • OCSP
      • SCEP Endpoints
        • DC Validation
        • Intune Validation
        • Jamf Validation
        • Static Validation
        • Static-AAD Validation
    • Certificate Master Settings
      • Basics
      • Microsoft Entra ID (Azure AD)
      • Logging
      • National Cloud Platforms
    • Application Artifacts
    • Certificate Master RBAC
    • Device Directories
    • Intune Strong Mapping
  • Other
    • Security & Privacy
    • Support
    • Licensing
      • Azure Marketplace
    • FAQs
      • General
      • Certificate Connector
      • Network Access Controllers
      • Renewing SCEPman Root CA
    • Troubleshooting
      • Common Problems
      • Certifried Security Vulnerability
      • Cisco ISE Host Header Limitation
      • Intune service discovery API permissions
      • Re-enrollment trigger
  • Uninstallation
  • Change Log
  • Links
  • SCEPman Website
Powered by GitBook
On this page
  • Workflow of issuing SCEP Certificates
  • Prerequisites
  • Google Workspace
  • Google Cloud Certificate Connector (GCCC)
  • SCEPman

Was this helpful?

  1. Certificate Management
  2. Other MDM Solutions

Google Workspace

Learn how to set up and configure certificate enrollment via SCEP for ChromeOS (Chromebook) using Chrome Enterprise and SCEPman.

Last updated 1 month ago

Was this helpful?

Workflow of issuing SCEP Certificates

  1. Chromebook generates a hardware-backed private key.

  2. Google generates a CSR with the SCEP profile.

  3. Connector forwards the CSR to SCEPman.

  4. SCEPman signs the CSR and sends the signed CRS back to the connector which forwards it to PubSub.

  5. PubSub sends the signed CRS to device management for temporary storage.

  6. Device management sends the signed CRS to the Chromebook where it is merged with the harware-backed private key. The signed CSR is deleted from temporary storage.

Prerequisites

Google Workspace

This guide assumes that you already provisioned Chromebook computer(s) running ChromeOS version 89 or later managed with Chrome Enterprise.

Google Cloud Certificate Connector (GCCC)

Prerequisites

  • The GCCC requires a Windows Server appliance or VM running Windows Server 2016 or later.

  • The Windows Server instance must have the following network access:

    • Outbound: HTTP (80) and HTTPS (443).

Installation of the GCCC

  1. In your Google Admin console (at admin.google.com) > Go to Menu > Devices > Network

  2. Click Secure SCEP > Download Connector.

  3. In the Google Cloud Certificate Connector section, click Download. The download creates a folder on your desktop that contains the certificate connector. We recommend you download the other connector configuration files to this folder.

  4. In the Download the connector configuration file section, click Download. The config.json file downloads.

  5. In the Get a service account key section, click Generate key. The key.json file downloads.

  6. Run the certificate connector installer.

    1. In the installation wizard, click Next.

    2. Accept the terms of the license agreement and click Next.

    3. Choose the account that the service is installed for and click Next. The account must have privileges to sign in as a service on the Windows server.

    4. Select the installation location. We recommend using the default. Click Next.

    5. Enter your service account credentials and click Next. The service installs.

    6. Click Finish to complete the installation.

  7. Move the configuration and key files (config.json and key.json) into the GCCC folder created during installation, typically: C:\Program Files\Google Cloud Certificate Connector.

  8. Launch the Google Cloud Certificate Connector service:

    1. Open Windows Services.

    2. Select Google Cloud Certificate Connector in the list of services.

    3. Click Start to start the service. Ensure that the status changes to Running. The service automatically restarts if the computer reboots.

If you download a new service account key later, restart the service to apply it.

SCEPman

Enable Google Workspace Integration by adding the following environment variables on SCEPman app service:

You can differentiate between the SCEPman App Service and the Certificate Master by looking for the App Service without the "-cm" in its name

Setting
Description
Value

Enable 3rd-party validation

true to enable, false to disable

generate a 32 character password

Days certificates issued via Google Workspace are valid

365

Store requested certificates in the Storage Account, in order to show them in SCEPman Certificate Master

true to enable, false to disable

Google, Google Workspace, ChromeOS and related marks and logos are trademarks of Google LLC.

Certificate signing requests sent to SCEPman for signing are authenticated with this secure static password Recommendation: Store this secret in .

(optional)

(optional)

For more information and references please visit or download the original PDF guide .

Google Workspace Admin Help
Configuring Certificate Enrollment for ChromeOS via SCEP
AppConfig:StaticValidation:Enabled
AppConfig:StaticValidation:RequestPassword
AppConfig:StaticValidation:ValidityPeriodDays
AppConfig:StaticValidation:EnableCertificateStorage
Azure KeyVault
Minimum subscriptions required
Drawing