Uploaded image for project: 'WSS4J'
  1. WSS4J
  2. WSS-335

SAML NotOnOrAfter Conditions not set correctly in certain circumstances

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.6.4
    • Fix Version/s: 1.6.5
    • Component/s: None
    • Labels:
      None

      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.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            coheigea Colm O hEigeartaigh
            Reporter:
            coheigea Colm O hEigeartaigh
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development