Metadata validity interval and fun with timezones

[Byte Flinger]

I don't want to derail the original thread so I won't go too much into it.
I'll perform a debugging on the issue as soon as find some more time.
Ideally I'd like a Shib SP in place for testing rather than the limited old
picketlink implementation I got working but finding time to learn the SP
hasnt been easy (and the fact that it's a standalone app rather than a
webapp which to my understanding requires an apache in front of it doesn't
make it any easier).

Thanks for the input.
On Oct 31, 2013 10:38 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> On 10/31/13, 5:27 PM, "Byte Flinger" <byteflinger at gmail.com> wrote:
>
> >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.
>
> If they're on track with each other, you're talking about comparing
> something issues seconds ago. I don't see how a time change can affect
> that comparison.
>
> > 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.
>
> That isn't possible, so you're overlooking some difference in the messages
> by definition here. That assumes it's not the simple case of an SP that
> doesn't implement skew and the servers are just a few seconds off. Which
> is, as I said, a bug in the SP.
>
> -- 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/d9f2a703/attachment.html