Werner, I just ran the TestJAXRPCHandler and saw the following request being sent on the wire, which seems to be enhanced for security (encryption applied etc.). Can you just let me know how to reproduce this issue and what should be the success criterion for this test. Thanks.
======= Request Data Start ============== POST /axis/services/Ping3 HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:9090 Cache-Control: no-cache Pragma: no-cache SOAPAction: "Ping" Content-Length: 5152 <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header> <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsu:Created>2005-06-06T15:28:51.546Z</wsu:Created> <wsu:Expires>2005-06-06T15:33:51.546Z</wsu:Expires> </wsu:Timestamp> <xenc:EncryptedKey> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <wsse:SecurityTokenReference> <wsse:KeyIdentifier EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier">Xeg55vRyK3ZhAEhEf+YT0z986L0=</wsse:KeyIdentifier> </wsse:SecurityTokenReference> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>rw0BUbCL0sJZ/7FjaxRbn5OMGz1O0L2EV6du0JyE9QYHC3Uj5xm91cVEQ8ZKw9Og0vWhZsTlNZ0Oa98aVL/vhcW/dbg67LJxku2Da+wZsFSANukhExH/tgCJfPI5p9BtnPeSExbfHYEdWcRiueqVAaL/OUcNFLmmXfbKbUjrmLA=</xenc:CipherValue> </xenc:CipherData> <xenc:ReferenceList> <xenc:DataReference URI="#EncDataId-4199273"/> </xenc:ReferenceList> </xenc:EncryptedKey> <wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-1776694" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">MIIDDDCCAfSgAwIBAgIQM6YEf7FVYx/tZyEXgVComTANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQjEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQ4wDAYDVQQDDAVBbGljZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAoqi99By1VYo0aHrkKCNT4DkIgPL/SgahbeKdGhrbu3K2XG7arfD9tqIBIKMfrX4Gp90NJa85AV1yiNsEyvq+mUnMpNcKnLXLOjkTmMCqDYbbkehJlXPnaWLzve+mW0pJdPxtf3rbD4PS/cBQIvtpjmrDAU8VsZKT8DN5Kyz+EZsCAwEAAaOBkzCBkDAJBgNVHRMEAjAAMDMGA1UdHwQsMCowKKImhiRodHRwOi8vaW50ZXJvcC5iYnRlc3QubmV0L2NybC9jYS5jcmwwDgYDVR0PAQH/BAQDAgSwMB0GA1UdDgQWBBQK4l0TUHZ1QV3V2QtlLNDm+PoxiDAfBgNVHSMEGDAWgBTAnSj8wes1oR3WqqqgHBpNwkkPDzANBgkqhkiG9w0BAQUFAAOCAQEABTqpOpvW+6yrLXyUlP2xJbEkohXHI5OWwKWleOb9hlkhWntUalfcFOJAgUyH30TTpHldzx1+vK2LPzhoUFKYHE1IyQvokBN2JjFO64BQukCKnZhldLRPxGhfkTdxQgdf5rCK/wh3xVsZCNTfuMNmlAM6lOAg8QduDah3WFZpEA0s2nwQaCNQTNMjJC8tav1CBr6+E5FAmwPXP7pJxn9Fw9OXRyqbRA4v2y7YpbGkG2GI9UvOHw6SGvf4FRSthMMO35YbpikGsLix3vAsXWWi4rwfVOYzQK0OFPNi9RMCUdSH06m9uLWckiCxjos0FQODZE9l4ATGy9s9hNVwryOJTw==</wsse:BinarySecurityToken> <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> <ds:Reference URI="#id-4199273"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <ds:DigestValue>YFG1Lg54pffl+cPcLcwcozGMU48=</ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue>MYzUhrIW6uuzidLYXWV9Hr497i3k8OevIJCzcfPYBRB3Vnmxlq+rb8cOGDQDYrYjhhzHAZJ/IHCYAtJ5Xog8PSN8Lgh3GJdpr1eCYnEVrPvQqYl7WYUVc3vTOJuq82nD/qnHrC7inqRyvTpKTx14JDZYb8SryJSpRebs6c0/o6s=</ds:SignatureValue> <ds:KeyInfo Id="KeyId-21716810"> <wsse:SecurityTokenReference wsu:Id="STRId-11424570" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:Reference URI="#CertId-1776694" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/> </wsse:SecurityTokenReference> </ds:KeyInfo> </ds:Signature> </wsse:Security> </soapenv:Header> <soapenv:Body wsu:Id="id-4199273" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <xenc:EncryptedData Id="EncDataId-4199273" Type="http://www.w3.org/2001/04/xmlenc#Content"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/> <xenc:CipherData> <xenc:CipherValue>piJjPVLxR8ZZbbEzs47qp/tB3nEgcyMkQmYa80UubkFN1mMBNMxJrGet9drsKZNc0vGRSxYMRVB4SZcZPJbAT85fxbpICV31eKh+FbaufmMc5NNcPShIbExBFTuyKA3N2JYbtiJpKPm0WHS1DIr0Vxj6u8M8WT9OKvlwF+Uq9psBNLtj8+0+JPB7MebKHYIVGX/N5Ecw96QAddNjd/rrhOYLMjsct04sEa4W46NLnW54YP0BJZhSIc/oUBI4HO0xr+KReteX4UJdC7BsbTq5cH0KvWtY1IgupTf5ArQXAL6O031ER0FUhl50X/PshMr8Z2EcW3nZMOK7wl3w7idZoSO7Y/XJ5sWRnLLDXw+mahH2xVg2e+6O2jWjTZbBE54AXiJsn0qtEX0fGCcQNJrJ/rOoFe3whEprkKNevMuKq6o1Zo7xzm8wlNXQLoVzRZBedOwg7BDOQH+PGQ4slfT+ZxKUYC4epML45L91nRRaoMa/rnF0ejYLCm7pFOW6pBjT17Nbmp9HJqoxXIejF9VUkxQpnN5fABpgoL3WFwFAcfVAaWeINz1HvQpZRLfgA7SSBesA3VAIuNc=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </soapenv:Body> </soapenv:Envelope> ======= Request Data End ============== On 5/27/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Venkat, > > Can you please figure out a way to fix this problem ASAP! (some work > around for setting the property for Axis 1.2 final AND a code fix for > latest CVS) > > thanks, > dims > > ---------- Forwarded message ---------- > From: Werner Dittmann <[EMAIL PROTECTED]> > Date: May 27, 2005 7:35 AM > Subject: Some problem with Axis and JAX-RPC > To: [EMAIL PROTECTED] > > > Dims, > > instead of bothering the whole list, just a report about a problem > I found during WSS4J tests: > > During the tests of the JAX-RPC compliant handler I've seen that the > original SOAP request is not replaced by the security enhanced > SOAP request. WSS4JHandler uses the following code to set > a new SOAPPart content: > .... > sPart.setContent(new StreamSource(new > ByteArrayInputStream(os.toByteArray()))); > .... > > I digged a little bit into the Axis sources and found (in SOAPPart.java) > that > the setting of new content only works if a property called > > *public* *static* *final* String ALLOW_FORM_OPTIMIZATION = > *"axis.form.optimization"*; > > is either not set or is defined as "true". > > When using the interop testcase for the WSS4JHandler this property is > set to "false", thus > preventing the handler to replace the SOAPPart content. This causes > errors in the tests. > > The main difference between the mentioned interop testcase and our other > interop testcases is, that only this specific testcase uses a fully > dynamic setup of the handler, i.e > does not use a client side deployment file. Pls refer to > TestJAXRPCHandler.java in test/interop. > > I haven't looked into the Axis sources in more detail, but it seems that > there are > some differences between deployment file and dynamic handler setup. > > Can you check that? > > Regards > Werner > > BTW, I've checked the ant target to generate a binary distributin, works > so far. > Also modified to use the enhanced timestamps, tests ok so far. Now I'm > doing some upgrades/remove of warings during Javadoc generation to get > a more clean distri. I'll checking during the weekend. > > Werner > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ >
