[WSS-335] SAML NotOnOrAfter Conditions not set correctly in certain circumstances

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.4
• Fix Version/s: 1.6.5
• Assignee: Colm O hEigeartaigh
• Reporter: Colm O hEigeartaigh
• Created: 20/Jan/12 11:19
• Updated: 05/Mar/12 13:21
• Resolved: 20/Jan/12 11:24

Description

The SAML NotOnOrAfter Conditions is not set correctly in certain circumstances, when creating SAML 1.1 and SAML 2 Assertions. This happens when the user adds a "ConditionsBean" in the CallbackHandler to create the SAML Token, but does not specify either notBefore, notAfter or tokenPeriodMinutes. In this case, a Conditions element is created in which the NotOnOrAfter time is the exact same as the NotBefore time.