SOAP Authentication to the webservice on proxy side

[#1]

Hi there,

I'm Matthieu DELMAS, and this is my first post on Apigee questions. Yeeah 🙂

So i'm blocking on something that might be very simple..

1. What am i doing?
   
   As the title of question says, i want to create an API proxy on a SOAP service. And this works fine "basically".
   
   But now i have to split some part of SOAP "envelope", to handle security between Apigee and the Webservice directly in Apigee (not from the client-side).
   What i need, is get the Body part of SOAP message provided by the client request (with postman setup) AND the Header part directly in some apigee policy that the client dont have to pass it each request because Apigee is doing it alone.
   
   The solution seems to be the AssignMessage component using <Add>. it works with http headers, but not with the <Header>...</Header> of the SOAP envelope..
   
   More interesting thing is, i can use <Set> to set the entire SOAP envelope, but again, not my point here...
   
   
2. What am i seeing?
   
   As expected, the request doesn't contains the <Header>...</Header>, even after apigee AssigneMessage policy it's the same ..
   
   Client (Postman) printscreen:
   

   

   
   Apigee AssignMessage printscreen:
   

   

   
   Apigee trace printscreen :
   

   

   
   You can see here that it added my http header Matthieu-DETECTION with the <Add> of AssignMessage component, but there is no <Header>...<Header> in SOAP envelope..
   
   
3. What are you expecting to see?
   
   What i finally want is, that because of <Add> of the AssignMessage (or other) component, the <soapenv:Header>...</soapenv:Header> added in the SOAP envelope like this :
   <soapenv:Envelope>
   <soapenv:Header></soapenv:Header> // Added by Apigee on each request for this proxy
   <soapenv:Body></soapenv:Header> // provided by client initiale request
   </soapenv:Envelope>

Ok, i hope you have enougth infos, just ask if not.

Thanks for helping me there !

Matthieu

ps: i love Apigee 🙂