It looks like E10 has both SOAP 1.1 and 1.2.
I can get 1.1 working in SoapUI, but I cannot get SOAP 1.2 to work.
Is there some secret way to configure it so I can use the SOAP 1.2 services from Epicor?
This is the response I’m receiving when trying to use the 1.2 services and, frankly, I don’t know enough about this to know what to do with it.
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
</s:Header>
<s:Body>
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/sc">a:BadContextToken</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="en-US">The message could not be processed. This is most likely because the action 'Erp:BO:Customer/CustomerSvcContract/GetByCustID' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.</s:Text>
</s:Reason>
</s:Fault>
</s:Body>
</s:Envelope>
Are you standing up the SOAP 1.2 binding in Web.config? NOTE - Integration APIs (Basic, soap 1.2, etc) are not in the Admin Console UI so you need to manually edit them.