|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
This is a bug.
According to the SAML2 Core Spec:
================================
2.5.1.2 Attributes NotBefore and NotOnOrAfter
The NotBefore and NotOnOrAfter attributes specify time limits on the validity of the assertion within
the context of its profile(s) of use. They do not guarantee that the statements in the assertion will be
correct or accurate throughout the validity period.
The NotBefore attribute specifies the time instant at which the validity interval begins. The
NotOnOrAfter attribute specifies the time instant at which the validity interval has ended.
If the value for either NotBefore or NotOnOrAfter is omitted, then it is considered unspecified. If the
NotBefore attribute is unspecified (and if all other conditions that are supplied evaluate to Valid), then
the assertion is Valid with respect to conditions at any time before the time instant specified by the
NotOnOrAfter attribute. If the NotOnOrAfter attribute is unspecified (and if all other conditions that are
supplied evaluate to Valid), the assertion is Valid with respect to conditions from the time instant specified
by the NotBefore attribute with no expiry.
If neither attribute is specified (and if any other conditions that
are supplied evaluate to Valid), the assertion is Valid with respect to conditions at any time.
If both attributes are present, the value for NotBefore MUST be less than (earlier than) the value for
NotOnOrAfter.
================================