Changes between Version 29 and Version 30 of T12_Security/WS-Security
- Timestamp:
- 20/09/06 15:26:25 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
T12_Security/WS-Security
v29 v30 105 105 Check the above against the pyXMLSec code as a form of validation. pyXMLSec e.g.s use enveloped style rather than reference list pointing to document elements that are encrypted. Write a test script to output the former in order to validate the result. 106 106 107 [20/09/06] Working version: 108 * generate encrypted message and decrypted using pyXMLSec code (fixed when added correct padding for multiple of block size - last byte is set equal to the number of padding bytes. 109 * pyXMLSec encrypted message decrypted with test code 110 107 111 == WSDL + WS-Security? == 108 112 The existing system uses WSDL so it would desirable to keep with this when integrating WS-Security. WS-!PolicyAttachment standard would seem to cover what we need but is it too new for the s/w support tools to be there?