<html><head></head><body><div>I think I found the root cause. I was under the impression that Jetty 9.3 would work, but it appears that 9.2 needs to be used with the configuration in question.</div><div><br></div><div>Sorry for the confusion.</div><div><br></div><div><br class="Apple-interchange-newline"><span style="font-family: monospace; white-space: pre;">--
Brandon McKean
IT / Systems
Linux Administrator
(540)568-4235</span></div><div><br></div><div><br></div><div>On Wed, 2015-07-15 at 14:00 +0000, Cantor, Scott wrote:</div><blockquote type="cite"><pre>On 7/15/15, 9:07 AM, "users on behalf of McKean, Brandon Scott - mckeanbs" <<a href="mailto:users-bounces@shibboleth.net">users-bounces@shibboleth.net</a> on behalf of <a href="mailto:mckeanbs@jmu.edu">mckeanbs@jmu.edu</a>> wrote:
<blockquote type="cite">
I think I managed to get it worked out, I used the wiki directions to enhance a jetty-base I had already started on and was able to get it working. However I needed to put configuration parameters inline instead of relying on https.mod. I also had to make
a keystore with it as the PKCS12 bit wasn't being honored.
</blockquote>
Those are all huge red flags that you should resolve before spending any time on the IdP.
-- Scott
</pre></blockquote></body></html>