Soap authentication

343 views
Skip to first unread message

olivie...@gmail.com

unread,
Jun 30, 2015, 11:50:15 AM6/30/15
to camunda-...@googlegroups.com
Hello,

after playing with Activiti I saw AMunda provides some Soap connector. so I want to use it for that purpose.

I am able to use your soap-request example (git provided) with its associated testcase. now I would like to make it simply work in our environment (soap web services with authentication).

in invokeSoapService.bpmn you have http fields like url/headers/content-type/....
among them is there any way to pass login/password also?

Thank you for your help
Olivier

Ingo Richtsmeier

unread,
Jun 30, 2015, 12:18:05 PM6/30/15
to camunda-...@googlegroups.com, olivie...@gmail.com

Sebastian Menski

unread,
Jun 30, 2015, 12:20:37 PM6/30/15
to camunda-...@googlegroups.com, olivie...@gmail.com, olivie...@gmail.com
Hi Olivier,

this depends how you SOAP authentication works. Could you provide a example of a request which is required to by our authentication. 

Cheers,
Sebastian

olivie...@gmail.com

unread,
Jul 2, 2015, 10:25:35 AM7/2/15
to camunda-...@googlegroups.com, olivie...@gmail.com
Hello Ingo,

Thank you for your answer I looked into soap-connector-with-ws-security example. this kind of authentication does not work in our case.

Sebastian, here is a WS example call via curl CLI:
curl -H 'SOAPAction: ""' -H 'Content-Type: application/soap+xml' -u login:password -d @doPing.txt 'http://localhost/webapi/DeviceWS?wsdl'

where doPing.txt file content is:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.ubiqube.com">
<soapenv:Header/>
<soapenv:Body>
<ws:doPing>
<address>127.0.0.1</address>
</ws:doPing>
</soapenv:Body>
</soapenv:Envelope>

ideally I wanted to pass login/password as .bpmn variables...

Regards,
Olivier

Sebastian Menski

unread,
Jul 2, 2015, 10:41:30 AM7/2/15
to camunda-...@googlegroups.com, olivie...@gmail.com, olivie...@gmail.com
Hi Oliver,

so you are using HTTP basic auth? Which is unrelated to SOAP. You could either add the username and password to the url like http://username:password@localhost/...
which can be tricky if you have a complex password. So the better way would be to set the Authorization HTTP header to the value "Basic XXX" where XXX is
the base64 encode value of "username:password". So for example if the user is demo and the password is demo you should set the HTTP header:

Authorization: Basic ZGVtbzpkZW1vCg==

Cheers,
Sebastian

olivie...@gmail.com

unread,
Jul 6, 2015, 10:06:27 AM7/6/15
to camunda-...@googlegroups.com, olivie...@gmail.com
Thank you Sebastian. your answer helped me fix the authentication.

Regards,
Olivier
Reply all
Reply to author
Forward
0 new messages