-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WS-Security headers #19
Comments
@eraad
Please check your request mapping structure.
It also would be helpful if you will post your mapping here. |
Hi @DeLaGuardo I tried it but did not work. Please, find my mapping below: => (def m (service/request-mapping srv))
=> {Envelope {Header {}, Body {sendBill {fileName {:__value {:__type string, :__optional? true}}, contentFile {:__value {:__type nil, :__optional? true}}, partyType {:__value {:__type string, :__optional?
true}}}}}}
=> (assoc-in m ["Envelope" "Headers"] [{"Header" {"Security" {"UsernameToken" {"Username" {:__value "a"} "Password" {:__value "c"}}}}}])
=> {Envelope {Header {}, Body {sendBill {fileName {:__value 1234-01-123F-1.XML}, contentFile {:__value #object[[B 0x5279f71 [B@5279f71]}}}, Headers [{Header {Security {UsernameToken {Username {:__value a}, Password {:__value c}}}}}]}}
=> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ser="http://service.sunat.gob.pe"><soapenv:Header/><soapenv:Body><ser:sendBill><fileName>1234-01-123F-1.XML</fileName><contentFile>[B@5279f71</contentFile></ser:sendBill></soapenv:Body></soapenv:Envelope> Please note that the mapping produced by |
Is it possible also to send your WSDL file as well? |
For sure, please find it attached (zipped). I just added two more files that are included (ns and XSD). |
So, I can confirm that this is a bug caused by wsdl with no information about headers. I will try to add ability to inject custom handlers to fix that. Probably will solve it during upcoming weekend. |
Thanks! I suspected that. I will keep an eye on the project! Shall I close this issue? |
Let's leave it open until resolved |
I have a similar issue. Would there be a chance to fix it?... if not - could you point me where to look for? maybe I can help fixing it somehow |
Hi!
I'm trying to build a request for a SOAP service that requires WS-Security headers. It expects a call like this:
I tried associating a map with the expected headers into the mapping like so:
The problem is that the
wrap-body
fn seems to ignore this. Can you shed a light on how to add this type of headers into the SOAP envelope? Thanks!The text was updated successfully, but these errors were encountered: