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

SecureConversationTokenFinderInterceptor stores the wrong token identifier

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.2.4
    • 2.2.5, 2.3
    • WS-* Components
    • None

    Description

      The SecureConversationTokenFinderInterceptor in CXF has this line:

      message.getExchange().put(SecurityConstants.TOKEN_ID, tok.getID());

      but it also stores the token like so:

      SecurityToken token = new SecurityToken(sct.getIdentifier(), created, expires);

      Then in AbstractBindingBuilder.getSecurityToken() it tries to find the token in the token store using SecurityConstants.TOKEN_ID, and an error of "No signature token id" is thrown. The SecureConversationTokenFinderInterceptor should store the Identifier of the SCT instead (getIdentifier, not getIDI()).

      Attachments

        1. cxf-2487.patch
          0.9 kB
          Colm O hEigeartaigh

        Activity

          People

            dkulp Daniel Kulp
            coheigea Colm O hEigeartaigh
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: