Michal Niklas; Thank you for your response. It seems to apply in my case since I need to receive the fault messages as well as the "success" response.
I have used soapUI to communicate with the server. I can get back both success and fault responses, but cannot process either of them. I applied the change described in your link to my axis2/rampart installation. I also added a "SecurityHeaderCheck" phase to the InFlow and InFaultFlow phase order definitions in axis2. I still have something missing as the custom handler does not engage in either "success" or "fault" test conditions. Regards; -Mike Pettigrew -----Original Message----- From: Michal Niklas [mailto:mn-op...@heuthes.pl] Sent: Monday, June 27, 2011 10:53 PM To: java-user@axis.apache.org Cc: Mike Pettigrew Subject: Re: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security Hello, W dniu 2011-06-28 01:09, Mike Pettigrew pisze: > Martin Gainty; > [...] > > I have written a custom handler per some other sample codes, but I > cannot get it to engage. I don’t know what is missing. > Have you tried to communicate with server using soapUI? This program can use WS-Security and shows what parts (signature, timestamp, encrypted message) server returns and shows HTTP "plain" response (encrypted, with HTTP headers). I had similar problem and it was server side fault to return 500 Internal Server Error with "normal" WS-Security response instead od 200 OK with the same response: http://stackoverflow.com/questions/5511643/axis2rampart-must-understand-check-failed-for-header-security Maybe in your case you also receive HTTP 500 Internal Server Error with WS-Security response? Regards, Michał --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
