<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Verdana" size="2"><span style="font-size:10pt;">
<div>Amy,</div>
<div> </div>
<div>I'm not sure where you're getting the security warning, but this reminds me of a problem that I used to have.</div>
<div> </div>
<div>If you're getting a security warning in Chrome or Firefox, it's probably because you're going from a secured site (https) to an unsecured site (http). When my college switched to a secured site (http to https), I kept on getting error messages whenever
I used the Primo deep search box embedded in my library webpage because the Primo URL was still using an unsecured site (http). Easiest way to fix the problem I described is to make sure that your origination site and the destination site are either both secured
sites (https) or both non-secured sites (http). Also, you can usually go from a non-secured site to a secured site with no problems at all, but if you go the other way, you'll get a security warning.</div>
<div> </div>
<div>Hope this helps.</div>
<div> </div>
<div><font face="Bradley Hand ITC" size="4"><span style="font-size:14pt;"><b>Lily Kun</b></span></font></div>
<div>Systems and Electronic Resources Librarian</div>
<div><font face="Calibri" size="2" color="#262626"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><img src="cid:image001.jpg@01CF17A6.5DF28AA0"><img src="cid:43C9F5977977A34A8B49FC5F96DE9220@namprd05.prod.outlook.com"></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://spscc.edu/library"><font face="Garamond" size="3" color="blue"><span style="font-size:12pt;"><u>https://spscc.edu/library</u></span></font></a></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="mailto:lkun@spscc.edu"><font face="Garamond" size="3" color="blue"><span style="font-size:12pt;"><u>lkun@spscc.edu</u></span></font></a></span></font></div>
<div><font color="#262626">360-596-5436</font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div> </div>
<div>?Amy,</div>
<div> </div>
<div> </div>
<div>If you're getting security warnings when clicking through EZProxy, then there isnt really an issue related to Ex Libris configuration going on here.</div>
<div> </div>
<div> </div>
<div>In fact, I don't see any of our ExL products impacted by this change in Chrome, except the PBO, which does currently uses http instead of https:</div>
<div> </div>
<div> </div>
<div> </div>
<div>Sounds like you're just experiencing an EZProxy security certificate issue of some kind</div>
<div> </div>
<div> </div>
<div>For best results these days, you really need to use a 'wildcard' SSL certificate for ezproxy, which I'm sure Adam will understand.</div>
<div> </div>
<div> </div>
<div>Could you post more specific info on how you generate the error you're seeing? And ideally a screenshot as well? I might be able to tell you more from that.</div>
<div> </div>
<div> </div>
<div> </div>
<div>Wade Guidry - <a href="mailto:wadeg@bigbend.edu">wadeg@bigbend.edu</a></div>
<div>Library Consortium Services Manager</div>
<div>Washington Community & Technical Colleges Library Consortium (WACTCLC)</div>
<div>509.760.4474</div>
<div>________________________________</div>
<div>From: Wactclc-primo <<a href="mailto:wactclc-primo-bounces@lists.ctc.edu">wactclc-primo-bounces@lists.ctc.edu</a>> on behalf of Whittaker, Shellie <<a href="mailto:ShellieW@bigbend.edu">ShellieW@bigbend.edu</a>></div>
<div>Sent: Monday, October 23, 2017 8:29 AM</div>
<div>To: WACTCLC Primo discussions</div>
<div>Subject: {Spam?} Re: [Wactclc-primo] [External] [ALMA-L] Ex Libris – HTTP Security Update</div>
<div> </div>
<div>Amy,</div>
<div> </div>
<div>You should definitely open a case for this…even if someone else has.</div>
<div> </div>
<div>Shellie Whittaker</div>
<div>WACTC Library Consortium</div>
<div><a href="mailto:shelliew@bigbend.edu<mailto:shelliew@bigbend.edu">shelliew@bigbend.edu<mailto:shelliew@bigbend.edu</a>> | (360) 452-5264</div>
<div> </div>
<div>From: Wactclc-primo [<a href="mailto:wactclc-primo-bounces@lists.ctc.edu">mailto:wactclc-primo-bounces@lists.ctc.edu</a>] On Behalf Of Herman, Amy</div>
<div>Sent: Monday, October 23, 2017 8:23 AM</div>
<div>To: WACTCLC Primo discussions <<a href="mailto:wactclc-primo@lists.ctc.edu">wactclc-primo@lists.ctc.edu</a>></div>
<div>Subject: [Wactclc-primo] FW: [External] [ALMA-L] Ex Libris – HTTP Security Update</div>
<div> </div>
<div>Has anyone yet opened a SF case to request a “special security certificate be provided by Ex LIbris in order to enable HTTPS connectivity”? We had hoped we’d solved the Chrome/Not secure warning issue by updating our ezproxy software and obtaining a
public security certificate for the server, but after doing that on Friday the problem persists today. I’m hoping that perhaps this extra step mentioned this morning by Ex Libris will help.</div>
<div> </div>
<div>Amy Herman</div>
<div>Library Faculty | Olympic College</div>
<div>1600 Chester Avenue | Bremerton, WA 98337 <a href="mailto:aherman@olympic.edu<mailto:aherman@olympic.edu">aherman@olympic.edu<mailto:aherman@olympic.edu</a>> | 360-475-7256</div>
<div> </div>
<div>From: Alma [<a href="mailto:alma-bounces@exlibrisusers.org">mailto:alma-bounces@exlibrisusers.org</a>] On Behalf Of Asaf Kline</div>
<div>Sent: Sunday, October 22, 2017 7:04 AM</div>
<div>To: Alma group <<a href="mailto:alma@exlibrisusers.org<mailto:alma@exlibrisusers.org">alma@exlibrisusers.org<mailto:alma@exlibrisusers.org</a>>></div>
<div>Subject: [External] [ALMA-L] Ex Libris – HTTP Security Update</div>
<div> </div>
<div>Dear colleagues,</div>
<div> </div>
<div>Recent security changes made by Google may cause use of HTTP pages to trigger a “Not Secure” warning on Chrome browsers.</div>
<div> </div>
<div>Here at Ex Libris, we have taken the necessary steps to address the matter.</div>
<div>If this is relevant to your institution, please click here<<a href="https://knowledge.exlibrisgroup.com/@api/deki/files/58263/Security_Update_Customer_Announcement_-Chrome_Security_Alert_for_Non-TLS_sites.pdf?revision=1">https://knowledge.exlibrisgroup.com/@api/deki/files/58263/Security_Update_Customer_Announcement_-Chrome_Security_Alert_for_Non-TLS_sites.pdf?revision=1</a>>
to learn more about which Ex Libris products support HTTPS and how to enable HTTPS on your systems.</div>
<div> </div>
<div>The full details can also be found on the Customer Knowledge Center: Chrome browser identifies connection as "Not Secure"<<a href="https://knowledge.exlibrisgroup.com/Cross_Product/Knowledge_Articles/Chrome_browser_identifies_connection_as_Not_Secure?mt-draft=false">https://knowledge.exlibrisgroup.com/Cross_Product/Knowledge_Articles/Chrome_browser_identifies_connection_as_Not_Secure?mt-draft=false</a>></div>
<div> </div>
<div>If you have any questions regarding this, please feel free to contact us by submitting a case through the Support Portal<<a href="http://exlidp.exlibrisgroup.com/">http://exlidp.exlibrisgroup.com/</a>>.</div>
<div> </div>
<div>Best regards,</div>
<div>Global Operations</div>
<div>Ex Libris, a ProQuest Company</div>
<div> </div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>