<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>
<blockquote type="cite">
<div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Sorry, Nate, host.name.removed was me. I pull out our real ldap server hostname before posting to the list.</span></div>
</blockquote>
<div><br>
</div>
<div>Ah, okay, thanks. This will probably have to wait for one of the developers then.</div>
<br>
<blockquote type="cite">
<div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 11pt;">We are running V2.4.2 as of this past Monday, so that’s not the case here.</span></div>
</blockquote>
</div>
<div><br>
</div>
<div>Yep, that'd be consistent with your logs, it looks like. I was more worried about the newly added code in Shibboleth not being compatible with SSLv3 being off. But really, I have no idea. That was just a hunch. For me, real stacktrace problems start
getting fixed by tracing the stack, I guess, and the devs can do that faster and better than me.</div>
</body>
</html>