<p>Server time (OS time) is the same on both. This was mot happening last time I tried so I suspect it has to do with the time change on Sunday. I do wonder why the other setup which apart from Shibboleth attribute and relying-party configuration (and the fact that it's installed on the cloud while the non-working one is installed on a redhat vm) is working fine though.</p>
<div class="gmail_quote">On Oct 31, 2013 10:20 PM, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 10/31/13, 5:10 PM, "Byte Flinger" <<a href="mailto:byteflinger@gmail.com">byteflinger@gmail.com</a>> wrote:<br>
<br>
>On a slightly related matter, I have system with a picketlink-based SP<br>
>test installation which talks to Shibboleth. I performed a complete<br>
>reinstallation of Shibboleth yesterday and have switched from using java<br>
>1.7.40 to 1.7.04 on Shibboleth and for some reason picketlink keeps<br>
>saying that the assertion is too old and rejects Shibboleths SAML answer.<br>
<br>
Well, are they skewed? If not, then the SP must have a bug.<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div>