Sahi supports HTTPS out of the box. Sahi Pro eases the pain by automatically accepting SSL certificates. Sahi ships with a root certificate and all other certificates will be signed by this root certificate, making SSL testing absolutely smooth.
But, for some reason if the browser reports a certificate error as shown below, then you will need to import the root certificate to the “Trusted Root Certificate Authorities” store.
To import the root certificate, click on the “SSL” link on dashboard.
Click “Yes” to import the certificate.
This should import the certificate successfully.
Once done, you should be able to access your HTTPS/SSL site.
In other cases:
<java>/binto your PATH variable. (Details on adding Java/bin to Path), or specify the full path to keytool.exe in
<sahi>/config/sahi.properties. keytool.exe is present in the
For eg. you could do
to add java\bin to the path before you start Sahi.
This may happen if there are multiple certificate dialogs being opened by the browser at the same time. When trying to automate HTTPS sites, first do a dry pass of the site with the proxy on, but without bringing up the controller. Only bring up the controller for record/playback after all certificates have been accepted. This used to happen on Firefox 2.
NOTE: YOU SHOULD NOT HAVE TO DO THIS ANYMORE. JUST FOLLOW THE FIRST TWO SECTIONS AND THINGS SHOULD WORK PROPERLY.
If the certificates do not get created in sahi/userdata/certs folder, you can follow these instructions to manually create the certificates. These instructions will appear on the Sahi proxy console if there was some problem in creating certificates.
Sahi is trying to create a certificate for domain:
If you are unable to connect to this https site, do the following:
Check on your filesystem to see if a file like
has been created.
If not, then create it by running the command below on a command prompt.
Note that you need ‘keytool’ to be in your path.
keytool comes with the JDK by default and is present in
Once you create that file, ssl/https should work properly for that site.
keytool -genkey -alias sahi.example.com -keypass sahipassword
-storepass sahipassword -keyalg RSA -keystore
"CN=sahi.example.com, OU=Sahi, O=Sahi, L=Bangalore, S=Karnataka, C=IN"
The files in certs can be copied over to other systems to make ssl/https work there.
Since 2008, we changed the dummy domain name that sahi uses to sahi.example.com. If SSL used to work properly but has now started becoming slow, clear the files in
<sahi_dir>/certs directory, and let Sahi make new ones again, by accessing those sites.