Changeset 4247


Ignore:
Timestamp:
30/09/08 10:10:23 (11 years ago)
Author:
pjkersha
Message:

Reinstated signing of Binary Security Token - WSS4J's signature verification handler can deal with this even though its signature handler doesn't seem to be configurable to sign this element.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • TI12-security/trunk/python/ndg.security.common/ndg/security/common/wssecurity/dom.py

    r4245 r4247  
    362362        refC14nAlg = c14nAlgOpt[self.refC14nIsExcl] 
    363363 
    364         log.info("Forcing use of exclusive C14N - inclusive C14N" 
     364        log.info("Forcing use of exclusive C14N - inclusive C14N " 
    365365                 "does not seem to work for ZSI.Canonicalize") 
     366         
    366367        # TODO: remove this line if ZSI.Canonicalize ever starts working with 
    367368        # inclusive NS 
     
    374375             
    375376            refID = refNode.attributes[(_WSU.UTILITY, 'Id')].value 
    376             # skip binary security token 
    377             # - NB, this cannot be signed by a java client using Rampart1.3 
    378             if refID == "binaryToken": 
    379                 continue 
    380377             
    381378            # Set URI attribute to point to reference to be signed 
     
    389386                                   subset=refSubsetList, 
    390387                                   **inclusiveNSKWs) 
     388             
    391389            # Calculate digest for reference and base 64 encode 
    392390            # 
Note: See TracChangeset for help on using the changeset viewer.