Metadata validity interval and fun with timezones

[Byte Flinger]

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.
On Oct 31, 2013 10:20 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> On 10/31/13, 5:10 PM, "Byte Flinger" <byteflinger at gmail.com> wrote:
>
> >On a slightly related matter, I have system with a picketlink-based SP
> >test installation which talks to Shibboleth. I performed a complete
> >reinstallation of Shibboleth yesterday and have switched from using java
> >1.7.40 to 1.7.04 on Shibboleth and for some reason picketlink keeps
> >saying that the assertion is too old and rejects Shibboleths SAML answer.
>
> Well, are they skewed? If not, then the SP must have a bug.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131031/d112be8f/attachment-0001.html