<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">I don't see it myself, I can't replicate these issues. I see that Ebsco has announced their databases are having issues now after a recent upgrade so perhaps that's what students are continuing to have issues with. If I get more specifics
I'll forward them. <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><img width="462" height="327" style="width:4.8125in;height:3.4062in" id="Picture_x0020_1" src="cid:image001.jpg@01D34BEA.301B6AD0"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Amy Herman<o:p></o:p></p>
<p class="MsoPlainText">Library Faculty | Olympic College<o:p></o:p></p>
<p class="MsoPlainText">1600 Chester Avenue | Bremerton, WA 98337<o:p></o:p></p>
<p class="MsoPlainText">aherman@olympic.edu | 360-475-7256<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">From: Wactclc-primo [mailto:wactclc-primo-bounces@lists.ctc.edu] On Behalf Of Guidry, Wade<o:p></o:p></p>
<p class="MsoPlainText">Sent: Monday, October 23, 2017 10:27 AM<o:p></o:p></p>
<p class="MsoPlainText">To: WACTCLC Primo discussions <wactclc-primo@lists.ctc.edu><o:p></o:p></p>
<p class="MsoPlainText">Subject: [External] {Spam?} RE: [Wactclc-primo] [ALMA-L] Ex Libris – HTTP Security Update<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">?Amy,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">If you're getting security warnings when clicking through EZProxy, then there isnt really an issue related to Ex Libris configuration going on here.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">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:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Sounds like you're just experiencing an EZProxy security certificate issue of some kind<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">For best results these days, you really need to use a 'wildcard' SSL certificate for ezproxy, which I'm sure Adam will understand.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">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.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Wade Guidry - wadeg@bigbend.edu<o:p></o:p></p>
<p class="MsoPlainText">Library Consortium Services Manager<o:p></o:p></p>
<p class="MsoPlainText">Washington Community & Technical Colleges Library Consortium (WACTCLC)<o:p></o:p></p>
<p class="MsoPlainText">509.760.4474<o:p></o:p></p>
<p class="MsoPlainText">________________________________<o:p></o:p></p>
<p class="MsoPlainText">From: Wactclc-primo <wactclc-primo-bounces@lists.ctc.edu> on behalf of Whittaker, Shellie <ShellieW@bigbend.edu><o:p></o:p></p>
<p class="MsoPlainText">Sent: Monday, October 23, 2017 8:29 AM<o:p></o:p></p>
<p class="MsoPlainText">To: WACTCLC Primo discussions<o:p></o:p></p>
<p class="MsoPlainText">Subject: {Spam?} Re: [Wactclc-primo] [External] [ALMA-L] Ex Libris – HTTP Security Update<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Amy,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">You should definitely open a case for this…even if someone else has.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Shellie Whittaker<o:p></o:p></p>
<p class="MsoPlainText">WACTC Library Consortium<o:p></o:p></p>
<p class="MsoPlainText">shelliew@bigbend.edu<mailto:shelliew@bigbend.edu> | (360) 452-5264<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">From: Wactclc-primo [mailto:wactclc-primo-bounces@lists.ctc.edu] On Behalf Of Herman, Amy<o:p></o:p></p>
<p class="MsoPlainText">Sent: Monday, October 23, 2017 8:23 AM<o:p></o:p></p>
<p class="MsoPlainText">To: WACTCLC Primo discussions <wactclc-primo@lists.ctc.edu><o:p></o:p></p>
<p class="MsoPlainText">Subject: [Wactclc-primo] FW: [External] [ALMA-L] Ex Libris – HTTP Security Update<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">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.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Amy Herman<o:p></o:p></p>
<p class="MsoPlainText">Library Faculty | Olympic College<o:p></o:p></p>
<p class="MsoPlainText">1600 Chester Avenue | Bremerton, WA 98337 aherman@olympic.edu<mailto:aherman@olympic.edu> | 360-475-7256<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">From: Alma [mailto:alma-bounces@exlibrisusers.org] On Behalf Of Asaf Kline<o:p></o:p></p>
<p class="MsoPlainText">Sent: Sunday, October 22, 2017 7:04 AM<o:p></o:p></p>
<p class="MsoPlainText">To: Alma group <alma@exlibrisusers.org<mailto:alma@exlibrisusers.org>><o:p></o:p></p>
<p class="MsoPlainText">Subject: [External] [ALMA-L] Ex Libris – HTTP Security Update<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Dear colleagues,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Recent security changes made by Google may cause use of HTTP pages to trigger a “Not Secure” warning on Chrome browsers.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Here at Ex Libris, we have taken the necessary steps to address the matter.<o:p></o:p></p>
<p class="MsoPlainText">If this is relevant to your institution, please click here<https://knowledge.exlibrisgroup.com/@api/deki/files/58263/Security_Update_Customer_Announcement_-Chrome_Security_Alert_for_Non-TLS_sites.pdf?revision=1> to learn more about which
Ex Libris products support HTTPS and how to enable HTTPS on your systems.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The full details can also be found on the Customer Knowledge Center: Chrome browser identifies connection as "Not Secure"<https://knowledge.exlibrisgroup.com/Cross_Product/Knowledge_Articles/Chrome_browser_identifies_connection_as_Not_Secure?mt-draft=false><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">If you have any questions regarding this, please feel free to contact us by submitting a case through the Support Portal<http://exlidp.exlibrisgroup.com/>.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Best regards,<o:p></o:p></p>
<p class="MsoPlainText">Global Operations<o:p></o:p></p>
<p class="MsoPlainText">Ex Libris, a ProQuest Company<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>