How to handle untrusted certificates with Google Chrome

[murdock]

Hi,

I want to run my automated tests against Google Chrome (currently on
Windows XP, Chrome v4) however I run into an
untrusted certificate page each time I visit our test environment's
login page as you are redirected from "http" to "https".
My tests predominantly start via the login page to authenticate to the
test environment with different test user accounts.

Scenarios I've tried:

* Using selenium server v2.0a2, started server using the "-
trustAllSSLCertificates" flag
* Using selenium server v2.0a2, started server using the "-
proxyInjectionMode -userContentTransformation https http"
flag
* From the 'untrusted certificate' page displayed on Google Chrome, I
saved and imported this certificate into the
"trusted root certificate" and "trusted publisher" tabs
* I also had Google Chrome allow the certificate, however, this is
only good for the initial session regardless
if I started my selenium server using the "-browserSessionReuse"
flag

The above trials all failed.

NOTE: Running the same automated tests against IE or FF run without
problems.

Any stellar minds out there that can help out either with any
workarounds|solutions to the above situation?

Thanks

[Santiago Suarez Ordoñez]

I don't think there's a current workaround for your problem.
I'd analyze the possibility of setting a cookie by hand that would help you skip that https login that Chrome can't handle for now.
Also, let me recommend you a great read about https problems with testing that could help you convince your team to avoid the use of https in development environments:
http://adam.goucher.ca/?p=1365

Santi

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.

[murdock]

Thanks Santiago. For now, we've set up 2 test environments - one
using https and the other as http. Now our automation team is able to
run our selenium tests using Chrome on Windows against the HTTP
environment.

Unfortunately the selenium RC (currently using 1.0.3) is unable to
handle Chrome on Mac OS X as the server logs show the selenium RC
server is trying to access the path to the "chrome.exe" file. Seems
to be a hard coded value some where in the selenium-server.jar file as
there's no detection of the user agent being a Mac rather than a PC.
I'll search other threads if anyone has come across a solution for
this item, if not, I'll make a new post.

On Mar 3, 10:19 pm, Santiago Suarez Ordoñez <santi...@gmail.com>
wrote:

> I don't think there's a current workaround for your problem.
> I'd analyze the possibility of setting a cookie by hand that would help you
> skip that https login that Chrome can't handle for now.
> Also, let me recommend you a great read about https problems with testing
> that could help you convince your team to avoid the use of https in
> development environments:http://adam.goucher.ca/?p=1365
>
> Santi
>

> > selenium-user...@googlegroups.com<selenium-users%2Bunsu...@googlegroups.com>

[Santiago Suarez Ordoñez]

Happy to hear you could move to simple http, that will save lots of headaches in the future.
Regards chrome on mac, it's not so easy. Changing the location strategy is not the only task needed to make it work.
At Sauce Labs we're working hard to do it and hope to have it done soon for a future release of Sauce RC (our own open source distribution of Selenium RC) and hopefully be able to push it to Selenium RC's trunk.

Santiago Suarez Ordoñez
Clients Success Engineer
Sauce Labs Inc
http://saucelabs.com

To unsubscribe from this group, send email to selenium-user...@googlegroups.com.

[Phil Chadwick]

I don't know if this is the same issue. The admin access to my domain is not trusted, I got so fed up with having to click through the hurdles to access it that I am now using Firefox to access my admin instead, this has the facility to easily manage exceptions.

[Mukesh otwani]

You can check below post
http://www.learn-automation.com/2014/09/how-to-handle-untrusted-ssl-certificate.html