Full-site SSL reflects our commitment to focus on security that was mentioned in a recent From the Desk of the CTO post. A second major driver of our prioritization of our full-site SSL initiative are future changes from some of the more prevalent browsers in the market.
With the October release of Chrome 62, Google will roll out phase II of their project to move to a more secure web. Users of Chrome 62 and later will receive the following Not Secure indicator in the URL when an input field is selected and the page is hosted over HTTP rather than HTTPS:
The visual change occurs next to the URL and only when an input field is selected. Incorrect interpretations have circulated that Google will not load the page at all and will instead load the more intrusive Your connection is not private privacy error that can be seen when a request is made of a domain with a corrupt SSL certificate. This will not be the case with Chrome 62. Please read the following post from Google if you would like more information related to Chrome 62 and planned changes dealing with security: Marking HTTP as Non-Secure.
iModules is pleased to announce that with the October 16th release, we will be able to provide your institution with the option to update your entire iModules-hosted website to full-site SSL. Each URL that is not a redirect needs a secure certificate, which iModules will procure on your behalf. One security certificate is provided at no additional charge. If you need additional secure certificates, there will be a charge. The cost of each certificate will be based on the number of certificates required, and if your institution has already purchased a branded SSL certificate for commerce transaction.
There are multiple support pages in the Full-Site SSL section. Once you have reviewed all of the details in this Full-Site SSL section and have determined that your organization wants to migrate to full-site SSL, you must opt-in in order to implement this on your Encompass site. You can view all details on opting in and the implementation process by reviewing the Full-Site SSL Implementation page. An email containing these instructions will also sent to primary contacts at your institution on October 17th.
If you still have questions after reviewing all of the full-site SSL details, please contact Application Support.
Next Article: Full-Site SSL FAQs