Additional XML prefixes when client receives SOAP fault
Hello, I have a problem with XML prefixes. When the SOAP message leaves the server with a fault the body looks like this: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="Id-25568549"> soapenv:Receiver ENFORCED ERROR THROWN CORRECTLY http://www.foo.net/test/xsd/sys/common";> 0010 ENFORCED ERROR THROWN CORRECTLY ENFORCED ERROR THROWN CORRECTLY AC10014E0123F082FFAD0001 2009-09-25T11:23:32.156+02:00 But the client takes this body out of the stream: http://www.w3.org/2003/05/soap-envelope"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="Id-25568549"> soapenv:Receiver ENFORCED ERROR THROWN CORRECTLY http://www.foo.net/test/xsd/sys/common";> 0010 ENFORCED ERROR THROWN CORRECTLY ENFORCED ERROR THROWN CORRECTLY AC10014E0123F082FFAD0001 2009-09-25T11:23:32.156+02:00 You can see that there is no prefix in the serviceFault tag on the server side but the client puts the prefix "axis2ns1" into the body. For me this is a problem because the body is signed on the server side and the client calculates the hash with this prefix. That leads to signature verification failure. Would be great if you can help me. Greetings Christian
Re: Rampart one way only
Hello, inside the axis2.xml you have the different flows (inFlow, OutFlow, InFault and OutFault). Just remove the phase "Security" from the OutFlow and the OutFaultFlow. Greetings Christian - original Nachricht Betreff: Rampart one way only Gesendet: Do, 23. Okt 2008 Von: RonnieMJ<[EMAIL PROTECTED]> > > Is it possible to have rampart NOT be concerned with security on a return > message in a synchronous transaction? > > Example: > I send to server X with security headers. They return an OK message or a > fault. Neither of which would have security heading information. > -- > View this message in context: > http://www.nabble.com/Rampart-one-way-only-tp20133511p20133511.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- original Nachricht Ende - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: A service ONLY over https and not http
Hi, I already tried this using the the tag inside the service.xml but when I start the AXIS server, I get the information that this tag is not supported in AXIS 2. Greetings Christian - original Nachricht Betreff: Re: A service ONLY over https and not http Gesendet: Fr, 19. Sep 2008 Von: Nandana Mihindukulasooriya Hi Christian, In the services.xml, you can add https to expose your service only using https transport. thanks, nandana On Fri, Sep 19, 2008 at 3:44 PM, Christian Mielke <[EMAIL PROTECTED]> wrote: Hello, I want to call one of my web services only by https and not by http. The service also shouldn't accept the requests over http. It only should accept the requests over https. Is there a possibility to configure this in the services.xml or somewhere else? Greetings Christian -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org --- original Nachricht Ende
A service ONLY over https and not http
Hello, I want to call one of my web services only by https and not by http. The service also shouldn't accept the requests over http. It only should accept the requests over https. Is there a possibility to configure this in the services.xml or somewhere else? Greetings Christian
Clientside or serverside?
Hello, I am writing a handler for my Axis 2.1.3 environment. The handler should only be used in the inflow of the server. Is there a possibility to see in the MessageContext if I am on clientside or on serverside? Greetings Christian
Re: Re: Policies in services.xml
OK thanks for your reply, but RAMPART needs the policy in the services.xml, or not? Or is there another way to specify the policy for RAMPART and not in the services.xml? Greetings Christian - original Nachricht Betreff: Re: Policies in services.xml Gesendet: Mo, 18. Feb 2008 Von: Amila Suriarachchi There are two things 1. Normally you can not set the Rampart specific polices in a wsdl file. So any way you have to add them to the services.xml 2. There is no need to add polices in the wsdl to the services.xml. At the deployment time, the deployment engine creates the AxisObject structure using the WSDL11ToAxisServiceBuilder. This correctly sets the polices to the AxisObject structure. thanks, Amila. On Feb 18, 2008 1:17 PM, Christian Mielke <[EMAIL PROTECTED]> wrote: Hello, I want to use WS-Policy for my Web-Services. So I add a policy inside my WSDL and then I use WSDL2JAVA to generate my code. When I use this tool, the services.xml gets also generated, but why isn't the used policy of the WSDL also written in the generated services.xml so that I only have to add the neccessary RAMPART parameters? Greetings Christian -- Amila Suriarachchi, WSO2 Inc. --- original Nachricht Ende
Policies in services.xml
Hello, I want to use WS-Policy for my Web-Services. So I add a policy inside my WSDL and then I use WSDL2JAVA to generate my code. When I use this tool, the services.xml gets also generated, but why isn't the used policy of the WSDL also written in the generated services.xml so that I only have to add the neccessary RAMPART parameters? Greetings Christian
Re: rampart doc
Hi Michelantonio! In Version 1.3 the configuration of RAMPART by code is deprecated (InflowConfiguration, OutflowConfiguration). So it is much better when you use the configuration by XML or by WS-Policy. You can find the examples, if you download the sources of RAMPART. Greetings Christian M - original Nachricht Betreff: rampart doc Gesendet: Fr, 15. Feb 2008 Von: Michelantonio Trizio Hi, I'd like to know where I can find an updated version of javadoc and example of Rampart module. If I try to use org.apache.rampart.handler.config.InflowConfiguration, eclipse says to me that this class is deprecated... I'd like to view example for rampart-1.3. Thank you MT -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] --- original Nachricht Ende
