Official Selenium Blog

February 8, 2012

A Note About the Cybervillains SSL Certificate

Filed under: Technical — shs96c @ 9:10 pm UTC

If you’re using Selenium RC to test websites hosted on a secure site (accessed using a URL starting with HTTPS), we strongly recommend that you upgrade to Selenium 2.19. This is because the Cybervillains certificate in previous versions will expire soon, and has been replaced in 2.19 with an updated one.

Our thanks to Patrick Lightbody, Ivan De Marino and Mark Watson and Neustar for taking providing the new certificate and the patch!


  1. What happen if we do not?

    Comment by Kanstantsin Sudzilouski — February 10, 2012 @ 2:35 pm UTC | Reply

    • Your tests against HTTPS will start failing.

      Comment by shs96c — February 10, 2012 @ 3:51 pm UTC | Reply

  2. I have upgraded my selenium-server-standalone.jar from 2.18 to 2.19 but when I run my tests with Firefox (both versions, 3.6.26 & 10) I get a SSL certificate error. My site is using HTTPS and the error that FF returns is:

    Error code: sec_error_unknown_issuer

    Looking at the certificate in Firefox, the certificate CN is not known.

    Does anyone know how to resolve this?

    Comment by mdgreenfield — February 10, 2012 @ 7:49 pm UTC | Reply

    • I should note that by accepting the certificate, my tests will continue and my tests will pass. The problem is that my settings are not persisted between tests.

      Comment by mdgreenfield — February 10, 2012 @ 7:51 pm UTC | Reply

      • This has been fixed in 2.20.

        Comment by shs96c — March 25, 2012 @ 10:37 pm UTC

  3. Word of warning – see as there appear to be issues using Selenium server 2.19.0 with Firefox to test HTTPS sites using the selenium RC API

    Comment by Mark — February 16, 2012 @ 2:58 pm UTC | Reply

  4. Is there a plan to look at the bug posted above (3373) before the old certificate expires at the end of March?

    Comment by Mark — February 29, 2012 @ 4:46 pm UTC | Reply

  5. Does this certificate expiration apply to Selenium 1.x too?

    Comment by bigdylan — March 16, 2012 @ 3:30 pm UTC | Reply

    • Yes. If you’re still using a selenium 1.x JAR, you must update that to a 2.x JAR. It’s a drop in replacement, so you won’t need to rewrite your tests!

      Comment by shs96c — March 25, 2012 @ 10:34 pm UTC | Reply

      • so for those who are interested, it is possible to get 1.x working with the new certificate, so it you like us, cannot make a switch like this as quickly as it needs to be made. Follow the following steps (note, we only use Firefox, so this only shows how to do this for Firefox, some steps shortened for brevity):

        1) Download new Selenium 2.x and pull out the sslSupport directory
        2) Replace the existing 1.x sslSupport directory with the new one
        3) Open up a selenium browser session, go to the Tools->Options->Advanced->Encryption
        4) Delete the existing CyberVillans certificate
        5) Import the new certificate
        6) go to about:support and click “open containing folder” to get to the Firefox profile directory
        7) Copy the cert8.db file and put this in the appropriate profile directories inside the Selenium JAR(s)

        You should be good to go..

        Comment by bigdylan — March 26, 2012 @ 4:23 pm UTC

  6. I have an issue with the cybervillains certificate. I am using selenium-server-standalone-2.28.0.jar. I have installed certificate on Windows 7, Fedora Linux, Windows Xp. However, the certificate is working on Windows 7 and Fedora Linux. In Windows Xp, the certificate is unable to open https sites on Google Chrome 24 browser.

    The Error logged is untrusted site, please provide proper certificate.

    Is there any changes to be made on the browser side to make https sites work.

    Please provide workarounds. Thanks in advance.

    Comment by Amar — February 7, 2013 @ 10:16 am UTC | Reply

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Blog at

%d bloggers like this: