Changes between Version 10 and Version 11 of T12_Security/WS-Security


Ignore:
Timestamp:
25/08/06 16:50:10 (13 years ago)
Author:
pjkersha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • T12_Security/WS-Security

    v10 v11  
    2525 
    2626 * Modified pyXMLSec sign3.py test code to sign an externally referenced XML doc. 
    27  * Written test code adapted from pyGridWare !GssSignatureHandler to verify the above.  This uses the canonicalization algorithm from ZSI.wstools.c14n and M2Crypto for verification: 
     27 * Written test code adapted from pyGridWare `GssSignatureHandler` to verify the above.  This uses the canonicalization algorithm from ZSI.wstools.c14n and M2Crypto for verification: 
    2828 
    2929{{{ 
     
    4242 * (21/08/06) Test sign code working with test version of verify and pyXMLSec verify code.  Care is needed with namespace declarations and canonicalization.  It seems that all namespaces should be included in a document subset whether they're referenced or not.  See Spec (http://www.w3.org/TR/xml-c14n) 
    4343 
     44=== Integration into ZSI === 
     45How best to integrate singature code into ZSI? 
     46 
     47For WS client side, `ZSI.Binding.Send` has `sig_handler` keyword which can be assigned to a signature handler class.  This must implement `sign` and verify methods.  These both take the same single argument of a `ZSI.writer.SoapWriter` instance.  `verify` indicates an invalid signature by raising an exception.  `GssSignatureHandler` the pyGridWare handler class raises a `VerifyError` type. 
     48 
    4449== XML Encryption == 
    4550Tackle digital signature first :)