Project

General

Profile

Actions

Bug #6650

closed

Force SSL for *.commons.gc.cuny.edu pages

Added by Boone Gorges about 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
-
Target version:
Start date:
2016-11-08
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Starting in January 2017, Chrome will start showing "insecure" notices to users for non-HTTPS pages that contain password forms. See eg https://www.cnet.com/news/chrome-warning-insecure-http-websites-expose-passwords-credit-card-numbers/

On the Commons, we have a password form on every page (for logged-out users, at least) - in the toolbar.

We should start forcing SSL everywhere we can. For the moment, this means commons.gc.cuny.edu and *.commons.gc.cuny.edu. Most mapped domains don't have SSL certificates.

I'm going to go ahead and put this in the pipeline for 1.10.3. The code-level change will be pretty simple, but we should double-check to make sure we catch non-secure assets leaking through before then.

Ray, you're a watcher here - if you think of any blocking issues, please let me know.


Related issues

Related to CUNY Academic Commons - Feature #5525: Mapped domains should be administered over *.commons.gc.cuny.eduResolvedRaymond Hoh2016-05-03

Actions
Actions

Also available in: Atom PDF