hi Again,
I been trying to solve this issue for a while now, it seems that acording to the documentation in axis2 1.4 this shouldn't happen but... it still happening to me. I have found the following: http://issues.apache.org/jira/browse/RAMPART-90 Where it says that the error was fixed and the 1.4 version has the patch to solve it. it also says that: "We have to add the security phase to in the axis2.xml to use Rampart from now on" Something that I already checked: ... * <module ref="rampart"/> <!-- rampart -->* ... <phaseOrder type="OutFaultFlow"> <!-- user can add his own phases to this area --> <phase name="soapmonitorPhase"/> <phase name="OperationOutFaultPhase"/> <phase name="RMPhase"/> <phase name="PolicyDetermination"/> <phase name="MessageOut"/> * <phase name="Security"/> <!-- security -->* </phaseOrder> it even says: "Errors while processing security header should be reported with correct fault codes as defined in the WSS 1.0 sections " But this part has been a little dificult to check because I don't know if :Client.AuthenticationFault</faultcode> is a correct standar fault code, I get somethin like this: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ "> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults";>* p:Client.AuthenticationFault*</faultcode> <faultstring>La autenticación contra el LDAP Falló</faultstring> <detail/> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Any ideas? I would greatly appreciate your help. ___________________________ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. On Thu, Oct 22, 2009 at 8:29 AM, m4rkuz <[email protected]> wrote: > Somebody? > > the thing is that the application is being installed in many different and > distant places, and every installation comes to different security > configuration errors, not registered ips, bad user/pass credentials, not > registered users etc, and all this errors generate correct coherent fault > string that can help to solve them, but all I get is an SOAP HEADER MISSING > error that don't help me to give support to the users. > > How can I get this <faultstring> for show in my App. > ___________________________ > Marcus Sánchez Díaz. > Enterprise Developer. > SCJP - SCWCD. > > > On Wed, Oct 21, 2009 at 11:01 AM, m4rkuz <[email protected]> wrote: > >> >> Hi Everyone, >> >> Got a question for you all, I have an application that uses Axis2 + >> Rampart, to consume some Secure Webservices, but I'm having troubles to >> display all the info in the errors the server returns, to ilustrate this I >> show the SOAP I recive from the server: >> >> <?xml version="1.0" encoding="UTF-8" standalone="no"?> >> <SOAP-ENV:Envelope xmlns:SOAP-ENV=" >> http://schemas.xmlsoap.org/soap/envelope/";> >> <SOAP-ENV:Body> >> <SOAP-ENV:Fault> >> <faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults >> ">p:Client.AuthenticationFault</faultcode> >> <faultstring>*La autenticación contra el LDAP Falló*</faultstring> >> <detail/> >> </SOAP-ENV:Fault> >> </SOAP-ENV:Body> >> </SOAP-ENV:Envelope> >> >> This happens because the user/password does not match, in my client app I >> wish to take this exact message (the one in bold, in the <faultstring> tag) >> but I only can get an "Axis2 SOAP header missing error" that says nothing to >> my final users... >> >> How can I capture this error message? >> >> (excuse my English, if better explanation is required, just ask) >> >> >> >> >> ___________________________ >> Marcus Sánchez Díaz. >> Enterprise Developer. >> SCJP - SCWCD. >> > >
