Receiving error when sending outbound soap message from workflow

akillius
Kilo Expert

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

1 ACCEPTED SOLUTION

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.


View solution in original post

11 REPLIES 11

Hi Andy,



Have you created the auth profile on your SOAP message?



find_real_file.png



The basic profile should contain the user id and password of the outbound SOAP message that your accessing.



Thanks


Please Hit like, Helpful or Correct depending on the impact of the response


giriraj
Giga Contributor

Andrew,



Does the webservice expect authentication ? If so, have you setup the SOAP message function with the authentication type as Basic as shown above by Alikutty.



Are you saying that that the SOAP call works fine when you lets say invoke using a Script Include and its failing only when you are using the workflow ?



Thanks


Please Hit like, Helpful or Correct depending on the impact of the response


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.


Hi Andrew Killius



I am also facing the same issue. please let me know how did you supply the login values as part of the workflow. is it in the sensor script. If yes, can you give me the sample of script which you have used.



Thank you.


I created a custom property to store that information.   In the workflow, I have a Run Script activity where I set workflow.scratchpad value to the property by using gs.getProperty() function like so:



workflow.scratchpad.user = gs.getProperty('<property for username');


workflow.scratchpad.pw = gs.getProperty('property for password');



Then in the SOAP call I just declare the variable property in the variables section like so:



user=${workflow.scratchpad.user}, password=${workflow.scratchpad.pw}