Hi!
However, SAML2-core on section 1.3.3 specifies that:
#### 1.3.3 Time Values
All SAML time values have the type `xs:dateTime`, which is built in
to the W3C XML Schema Datatypes specification [Schema2], and **MUST
be expressed in UTC form, with no time zone component**.
According to Scott Cantor, this is misexpressed and should be read as
"MUST be expressed in UTC form, with no time zone _offset_":
https://lists.oasis-open.org/archives/saml-dev/201310/msg00001.html
I have no idea why this has never been addressed by a SAML erratum, as
this topic has popped up a number of times in the past (at least in the
context of SSP and eduGAIN).
Note that at the very least SSP and Shibboleth will break if non-
ISO8601-compatible dates are received, so please don't generate any
unqualified dates. I don't really have an opinion about _accepting_
such unqualified dates, though.
Bas.
--
Bas Zoetekouw
SURFnet Trust & Security
✉ Moreelsepark 48, Utrecht NL-3511EP
✆ +31-88-7873-562