If you have a webpage that is secured using a self-signed or otherwise invalid certificate, you will likely run into issues of the browser in a test session telling you the certificate is invalid. While this is expected behavior, and a boon to security, it can make testing, especially automated testing or screenshots, more difficult than it needs to be.
Fortunately, we have recently implemented a way to allow invalid certificates in your testing!
Using the acceptAllCerts feature
You can use our cbt_tunnels tool, available through NPM (
npm install -g cbt_tunnels ) to use this feature.
- Ensure you are using the latest version of the<
npm update -g cbt_tunnels
- Start the cbt_tunnels module using the
cbt_tunnels --username YOUR_USER_NAME --authkey YOUR_AUTH_KEY --acceptAllCerts --bypass false. Be especially sure to include the bypass option if you are testing a publicly-accessible resource.
- Start your test.
You can also use our binary.
- Click the local connection button then use the download link to get the latest binary for your OS.
- Start the local connection using the command
cbt-tunnels-YOUR_PLATFORM --username YOUR_USER_NAME --authkey YOUR_AUTH_KEY --acceptAllCerts --bypass false
- Start your test.
Using the Chrome extension
You will need to install our Chrome extension using the link provided in the Chrome browser.
- Start your local connection by ensuring that the Bypass Local Connection checkbox is unchecked and that the Allow Insecure SSL Certificates checkbox is checked.
- Enable and start your test.
Using the Safari Browser
When testing a site with an invalid or self-assigned certificate using the Safari Browser without a local connection you will receive a warning.
To accept the invalid certificate
As always, if you have any questions or concerns about how to use this or how it works, don’t hesitate to reach out to us via our in-app chat feature or by emailing us at email@example.com.