Skip to content

Instantly share code, notes, and snippets.

@mowings

mowings/README.md

Last active March 6, 2018 21:47
Show Gist options
  • Save mowings/524eee5651a187471b89c94b8aadac07 to your computer and use it in GitHub Desktop.
Save mowings/524eee5651a187471b89c94b8aadac07 to your computer and use it in GitHub Desktop.
Download ZIP
Getting Chrome to trust a self-signed cerificate on OSX
Raw
README.md

Getting chrome to trust a self-signed cerificate on OSX

These instructions are valid as of v 61.

  • Point your browser at the site with the self-signed cert.
  • Allow chrome to load the site
  • Bring up the developer console and switch to the security tab
  • Be sure the only error is that there is no, or an untrusted cert signer. Other errors are possible (like no SANs defined, for instance). You might as well go ahead and fix any other errors before proceeding, or this will all be for nothing. The most common issue with Chrome is that no Subject Alt Names (SANs) are defined. Chrome will not trust your cert without these.
  • Click "View Certificate" button
  • Drag the certificate icon to your desktop or a finder window. This will export the cert to a file.
  • Open up your keychain manager, be sure the Keychain Viewer window is open, and drag the exported cert into the System folder
  • Right click the cert, select "GetInfo"
  • Expand the "Trust" menu
  • Change "When using this certificate" to "Always Trust"
  • Close out the Keychain app
  • You'll probably need to restart chrome
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment