- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2017 12:34 PM
I am working on an outbound soap call to a different application. The SOAP message was built with the correct WSDLs and the corresponding SOAP Functions are setup. When I do a test in from the SOAP Message itself, it is successful. Once I proved that, I attempted to add this SOAP Message to a workflow. When the workflow tries to execute the SOAP Message it consistently fails. When I look at the workflow activity, I am seeing the following message:
"This object does not support the auth profile of this SOAP message function, please use SOAPMessageV2"
I struggling to understand why this is working in the SOAP Message directly but not in the workflow. Anyone have any ideas of why I am hitting this?
Thanks!
Andy
Solved! Go to Solution.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2017 06:06 AM
Thanks everyone for their responses but I ended up finding an even simpler solution. By removing the Basic Authentication value in the SOAP Message and supply the login values as part of the workflow, I get the expected result. When you have a value in the Basic Authentication value it forces the SOAPMessageV2 script. By leaving it blank, it uses the SOAPMessage which is more compatible when calling the SOAP Message activity in a workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2017 05:32 AM
If i have a user name is 'xyzuser' and password is 'test123' then where exactly these values come in the script?
Regards,
Mohammad Ziyad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2017 09:56 AM