https://answers.axonivy.com/questions/3185/how-to-avoid-policy-error-when-calling-soap-webservices<p>I'm integrating data from a remote SAP system over SOAP services. The SAP services WSDL contains <code>Policy</code> elements. At runtime the remote call fails with <code>PolicyException: None of the policy alternatives can be satisfied.</code> Does anybody know how to call such a service?</p> <p><img alt="bpmError" src="https://answers.axonivy.com/upfiles/webserviceExceptionPolicy.png"> <img alt="policyWsdl" src="https://answers.axonivy.com/upfiles/wsdlWithOptionalPolicies.png"></p>enWed, 11 Apr 2018 05:46:29 -0400https://answers.axonivy.com/questions/3185/how-to-avoid-policy-error-when-calling-soap-webservices/3186<p><strong>7.1.0 and newer:</strong></p> <p>You have two possibilities, when using <code>Apache CXF</code> as your client library:</p> <ol> <li> <p><strong>Ignore all policies</strong>: Many policies are optional and can be completely ignored. You can do this bis adding the feature <code>IgnoreAllPoliciesFeature</code> to your client web service configuration. <img alt="alt text" src="https://answers.axonivy.com/upfiles/ignorePolicyConfig.png"></p> </li> <li> <p><strong>Ignore some policies</strong>: By adding the feature <code>IgnorePolicyFeature</code> you can specify with the property <code>policy.ignore</code> which policies you want to ignore in your web service client. The property value is a comma-separated list of form <code>namespaceURI:policy</code>, e.g.</p> <p><code><a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy:SupportingTokens,http://schemas.xmlsoap.org/ws/2005/07/securitypolicy:RecipientToken">http://schemas.xmlsoap.org/ws/2005/07/securitypolicy:SupportingTokens,http://schemas.xmlsoap.org/ws/2005/07/securitypolicy:RecipientToken</a></code> <img alt="alt text" src="https://answers.axonivy.com/upfiles/IgnorePolicyFeature_pVDNj5g.png"></p> </li> </ol> <hr> <p><strong>7.0 LTS and older</strong></p> <p>Many policies are optional and can be completely ignored. But the integrated <code>Axis 1</code> and <code>Axis 2</code> libraries are not able to handle them. The only way out is to patch the WSDL service definition. Remove all <code>Policy</code> declarations and their references and generate your service again against this modified WSDL.</p>Reguel WermelingerWed, 11 Apr 2018 05:46:29 -0400https://answers.axonivy.com/questions/3185/how-to-avoid-policy-error-when-calling-soap-webservices/3186