Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-5278

STS Renew returns incorrect lifetime

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.7.6
    • 2.6.10, 2.7.7
    • STS
    • None
    • Unknown

    Description

      SAMLTokenRenewer#renewToken sets the lifetime attribute of the TokenRenwerResponse to the difference between the NotBefore and NotOnOrAfter attributes of the SAML assertion conditions. Later the TokenRenewOperation#createREsponse method creates a Lifetime using the current timestamp as the Created value and the current timestamp plus the previously calculated difference as the Expires.

      In cases where the NotBefore of the SAML assertion conditions is not the current time this results in an incorrect lifetime in the response from the renew operation. For example, if the NotBefore is a few minutes in the past to work around systems with clock differences then the lifetime in the response will claim the token expires a few minutes before it actually does.

      This seems to cause issues with caching of tokens on the client side (STSClient) as the token will be cached for a period shorter than it should be.

      Attachments

        Issue Links

          Activity

            People

              coheigea Colm O hEigeartaigh
              ethan.wallwork Ethan Wallwork
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: