Chrome CAC Settings

Chrome CAC Configuration Overview

CAC workstation setup

Google Chrome uses the Windows certificate store for CAC authentication, which means it generally works well once your Windows system is properly configured. Chrome has become one of the more reliable browsers for DoD site access, especially after Microsoft transitioned Edge to the Chromium engine. This guide covers Chrome-specific settings and troubleshooting.

Prerequisites for Chrome CAC Access

Before configuring Chrome-specific settings, ensure your Windows system is ready:

  • CAC reader drivers installed: Your reader should appear in Device Manager without warnings
  • Middleware installed: ActivClient, 90Meter, OpenSC, or Windows built-in support
  • DoD certificates installed: Root and intermediate certificates in Windows certificate store
  • Smart card services running: Check Windows Services for smart card-related services

If these prerequisites aren’t met, Chrome won’t be able to access your CAC regardless of browser settings.

Chrome Certificate Settings

Chrome’s certificate management is accessible through Settings:

  1. Click the three-dot menu → Settings
  2. Click “Privacy and security” in the left sidebar
  3. Click “Security”
  4. Scroll down to “Manage certificates”

This opens the Windows Certificate Manager (same as running certmgr.msc), where you can:

  • View installed DoD root certificates under “Trusted Root Certification Authorities”
  • Check intermediate certificates under “Intermediate Certification Authorities”
  • View your personal certificates under “Personal” (certificates from your CAC appear here when inserted)

Unlike Firefox, Chrome doesn’t maintain its own certificate store, so any certificates installed in Windows are automatically available to Chrome.

Chrome Flags for CAC Compatibility

Chrome includes experimental features called “flags” that can improve CAC compatibility. Access these by typing chrome://flags in the address bar:

Flag Setting Purpose
#allow-insecure-localhost Enabled Helps with some local DoD applications that use self-signed certificates
#enable-webrtc-hide-local-ips-with-mdns Default or Disabled May interfere with some DoD video conferencing – disable if issues occur

Most users won’t need to modify Chrome flags for basic CAC authentication. Only change these if you’re experiencing specific issues and have been advised to do so.

Site Settings for DoD Websites

Some DoD sites may require specific Chrome permissions:

  1. Navigate to the DoD site
  2. Click the padlock or tune icon in the address bar
  3. Click “Site settings”
  4. Review and adjust permissions as needed:
    • Cookies: Set to “Allow” for sites that require session persistence
    • JavaScript: Must be “Allow” for most DoD applications
    • Pop-ups: Some DoD sites use pop-ups for authentication or document viewing

Chrome Profile Considerations

Chrome profiles can affect CAC authentication:

  • Personal vs. Work profiles: If you have multiple Chrome profiles, CAC authentication should work in any profile since it uses Windows certificates
  • Guest mode: CAC authentication typically works in guest mode, but cookies and preferences won’t persist
  • Incognito mode: CAC works in incognito, useful for troubleshooting cookie-related issues
  • Managed Chrome: If your organization manages Chrome through enterprise policies, some settings may be locked

If CAC works in one profile but not another, compare settings between profiles or try creating a fresh profile for DoD access.

Clearing Chrome Data for CAC Issues

When troubleshooting CAC authentication problems, clearing cached data often helps:

  1. Press Ctrl+Shift+Delete to open Clear Browsing Data
  2. Select “All time” for the time range
  3. Check “Cookies and other site data”
  4. Check “Cached images and files”
  5. Click “Clear data”

For persistent issues, also try:

  • Clearing SSL state: Settings → Privacy and security → Security → Manage certificates → (in Windows dialog) Clear SSL state
  • Removing saved passwords for DoD sites if you’ve accidentally saved credentials

Troubleshooting Chrome CAC Issues

  • No certificate prompt appears:
    • Verify your CAC is inserted and recognized by your middleware
    • Check that smart card services are running in Windows
    • Try the site in Edge – if it works there, the issue is Chrome-specific
    • Clear cached data and SSL state
  • Wrong certificate selected:
    • Chrome may remember your certificate choice – clear browsing data
    • Remove the site’s exceptions in Site Settings
    • If you have multiple CACs or certificates, ensure the correct one is selected when prompted
  • “Your connection is not private” error:
    • DoD root certificates may not be installed – run InstallRoot or import certificates manually
    • Check that the system date and time are correct – certificate validation fails with wrong dates
    • The site’s certificate may have actually expired – try a different DoD site to test
  • ERR_SSL_CLIENT_AUTH_CERT_NEEDED:
    • Site requires a certificate but Chrome isn’t offering one
    • Check middleware is recognizing your CAC
    • Verify certificates appear in Windows certificate store under Personal
  • Slow or hanging authentication:
    • Chrome may be checking certificate revocation – this can be slow on some networks
    • Try temporarily disabling “Check for server certificate revocation” in Windows Internet Options (not recommended for permanent use)
    • Network issues reaching OCSP servers can cause delays

Chrome Enterprise Policies

Organizations may deploy Chrome with specific policies for CAC access. Common policies include:

  • AutoSelectCertificateForUrls: Automatically selects a certificate for specific sites, eliminating the selection prompt
  • AuthServerAllowlist: Defines which servers can use integrated authentication
  • EnterpriseRealTimeUrlCheckMode: May affect how Chrome handles DoD site security

If you’re on a managed computer and CAC authentication behaves unexpectedly, contact your IT department – enterprise policies may be affecting Chrome’s behavior.

Chrome Updates and CAC Compatibility

Chrome auto-updates frequently, and occasionally an update affects CAC functionality:

  • If CAC stops working after a Chrome update, check militarycac.com or DoD forums for known issues
  • Try Edge as a backup browser while waiting for a fix
  • Enterprise users may be able to roll back to a previous Chrome version through their IT department
  • Report issues to your IT help desk so they can track and escalate if needed
John Bigley

About John Bigley

John Bigley is a former DoD IT specialist with over 12 years of experience supporting CAC authentication systems and military network infrastructure. He specializes in troubleshooting smart card issues and helping service members navigate DoD technology requirements.

John Bigley

John Bigley

Author & Expert

John Bigley is an electrical engineer and EV enthusiast who has been driving electric vehicles since 2015. He has installed over 200 home charging stations across the Pacific Northwest and consults on commercial EV infrastructure projects.

19 Articles
View All Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

Subscribe for Updates

Get the latest articles delivered to your inbox.