The problem is that I can't alter anything from client side, so the request body is missing outsystem url namespace and header is missing SOAPAction KEY, fixing either of this will get me the request body, otherwise it will rejected by IIS.
I'm trying to do something with factory configuration but so far not working
Any suggestion?
Regarding the initial question, don't think it is possible to add incoming headers. Request headers are usually read-only in the IIS pipeline after the isapi filters stages.
As for the SOAP Extensibility suggestion, not sure if it will help as well, since it's for SOAP "Consume", not "Expose".
I'm not sure what the actual use case here is since you say you have no control of the client. The SOAP Expose is not design to give full control and give you expressiveness to match a generic client target to it. It's meant for the client to respect the signature of what is being exposed, and not the other way around. So the flexibility there is limited.
That said, regarding the "namespace" part, there is a little control there.Scroll down on the module properties (the actual Module in the tree, not the SOAP itself) and there is a "Web Services Namespace" that will have some effect over the namespaces and soap actions of the exposed SOAP services in that module
thank you! will try : )
works like a charm 😂, I actually wrote a extension for the problem I'm facing, but this will solve the namespace part, wish I had noticed it sooner.
Please try the existing Forge component, SOAP Extensibility from Outsystems, to alter the request for your header.SOAP Extensibility