Support HTTPS in webbrowser-app autopilot test suite

[Olivier Tilloy]

The webbrowser-app autopilot test suite currently uses a test HTTP server. In the near future, it will need to gain support for HTTPS for some tests (e.g. those that embed getUserMedia() calls in HTML):

    [JS] (:0) getUserMedia() is deprecated on insecure origins, and support will be removed in the future. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.

[Olivier Tilloy (osomon)]

This would be useful to automate the testing of the invalid/expired certificate pages too.

[Olivier Tilloy (osomon)]

Bumped the importance to high as the following test is now failing with oxide 1.11 (to be released soon):

     webbrowser_app.tests.test_media_access_permission.TestMediaAccessPermission.test_deny

The message we’re getting from oxide is:

    [JS] (:0) getUserMedia() no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.

[Olivier Tilloy (osomon)]

To add HTTPS capabilities to the autopilot test suite, we need a way to inject custom root certificates into oxide. Oxide has a test helper called oxideSetNSSDbPath(…) but it’s not a public API, so it can’t be used by webbrowser-app. There is also a patch in oxide that removes the ability to load a shared NSS database from $HOME/.pki/nssdb/, so we can’t point $HOME to a temporary directory and add custom certificates there.

According to https://bugs.launchpad.net/oxide/+bug/1260048/comments/10, chromium is going to move away from NSS at some point in the future anyway.

This bug is now blocked on oxide using a custom, application-specific place to store custom certificates.

[Olivier Tilloy (osomon)]

I’ve submitted a branch that temporarily skips the one autopilot test that requires HTTPS starting with oxide 1.11 (about to be released).

[Olivier Tilloy (osomon)]

I’ve filed bug #1522513 to track the lack of a way to specify a custom certificates db for oxide.

[Olivier Tilloy (osomon)]

Starting with oxide 1.14, geolocation API calls are blocked on insecure origins, so the following webbrowser-app autopilot tests will start failing:

webbrowser_app.tests.test_geolocation.TestGeolocation.test_geolocation_accept
webbrowser_app.tests.test_geolocation.TestGeolocation.test_geolocation_deny