<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 17, 2015 at 10:34 AM, Rich Graves <span dir="ltr"><<a href="mailto:rgraves@carleton.edu" target="_blank">rgraves@carleton.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>> Do you actually know what they changed that broke it?<br>
<br>
</span>Nope, just checking if someone else had already run into this. Guess not.<br></blockquote><div><br></div><div>I just upgraded on the Mac. Using the unlimited strength policy files, I didn't see any issues performing some basic tests.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I've got meetings next couple hours but will return to it in the afternoon. The RHSA mentions two crypto-ish things.<br>
<br>
Backing down the stack trace a little (I have *not* yet taken the time to look at what's in my trust store):<br>
<br>
Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty<br></blockquote><div> </div><div>Some things to check...</div><div>When you upgraded did you lose your cacerts file or is it corrupted?</div><div>Are you specifying a custom truststore/certificate in your LDAP config? Can that still be read?</div><div><br></div><div>--Daniel Fisher</div><div><br></div></div></div></div>