Changes between Version 31 and Version 32 of T12_Security/WS-Security


Ignore:
Timestamp:
22/09/06 16:48:40 (13 years ago)
Author:
pjkersha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • T12_Security/WS-Security

    v31 v32  
    121121Conversation with Joshua Boverhof (08/09/06): pyGridWare does use document literal style WSDL with ZSI.  Current code simply signs the whole of SOAP message body.  It doesn't sign individual fields. 
    122122 
    123 [22/09/06] Updated ZSI from official 2.0_rc2 release to release 1252 from the Sourceforge pywebsvcs SubVersion repository.  pyGridWare now works and successfully created test code using pyGridWare wsdl2web which creates a WS using Twisted. 
     123[22/09/06] Updated ZSI from official 2.0_rc2 release to release 1252 from the Sourceforge pywebsvcs !SubVersion repository.  pyGridWare now works and successfully created test code using pyGridWare wsdl2web which creates a WS using Twisted. 
    124124 
    125125Also adapted the Echo WSDL example from the ZSI 1252 release.  Created a document literal style WSDL from the existing RPC encoded NDG SimpleCA WSDL and created client and server code adapting from the ZSI Echo example.  Also added in signature handling code for client and server: the server side has `wsdl2dispatch` generated code which includes a class which inherits from `ZSI.ServiceContainer.ServiceInterface`.  This includes stubs for `sign` and `verify` methods which can be overridden as required to provide server side digital signature functionality. 
     126 
     127== Twisted or not? == 
     128With the current ZSI release 1252 code it's possible to integrate WS-Security at least for digital signature and with some modification, encryption.  Is it worth using the extension to ZSI with Twisted?  This needs investigating in the pyGridWare code and any refs online to using Twisted.