SSL Error: alert internal error

[Christopher Peters]

You are correct about it being Tomcat native.  That was bad information on
my part.  When I initially set up the IDP v1 server we used Apache through
Tomcat, but when we migrated to 2.1.5 we went native Tomcat and I
completely forgot about that change.

--

I think the bad cert issue is that we self-sign the cert.  It's only used
through InCommon and in Metadata, so it doesn't need to go through
verification.  We are aware it expires in 3 days, and that is why there is
a second cert in InCommon Metadata which is soon to replace this one.


On Mon, Jul 29, 2013 at 2:21 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> I would add that if the server's headers are to be believed, that is *not*
> Apache, it's Tomcat.
>
> So yes, I suspect you have an issue with the Java stack here, if that's in
> fact the TLS implementation in use.
>
> Various TLS bugs hit in the middle of the 1.6 JDK cycle, I'd strongly
> suggest moving to 1.7, or if absolutely necessary the latest 1.6 and go
> from there.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Chris Peters
Middleware Services Developer
Office of Information Technology - NSP
(949) 824-6845
cjpeters at uci.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130729/d405a5cb/attachment.html