Overview
Most SOAP use cases can and should be handled using native Appian features like Integration Objects. This plug-in specifically is suited for handling SOAP services with SOAP and Base64 attachments
Key Features & Functionality
The Advanced Call Web Service provides support for the following:
The Service Authentication section in the documentation lists the following supported authentication methods:
Is this plugin supports username + x509 key authentication as SAML, LDAP, x509, UsernameToken derived key, SignedSupportingTokens, or other authentication schemes are not supported within Call Web Service Smart Service
The SunCertPathBuilderException was resolved after uploading java keystore. Thanks.
What is the maximum response body size handled?
Thanks for providing the fix. No more observing AbstractCallSOAPWebService error.
I am running into following issue. could you please suggest if I am missing anything.
Can I use this smart service for the SOAP service which needs basic authentication (username and password).
I tried with "Service Authentication" parameter value as mentioned below however it fails.
Service Authentication:
{action: "USERNAME_TOKEN_DIGEST_PASSWORD", usernameTokenSystemKey: "scs.key"}
Error:
com.sun.xml.ws.client.ClientTransportException: HTTP transport error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Version 1.4.2 of the smart service should be published shortly to the App Market.
It should resolved this issue.
Are there any other errors in the tomcat-stdOut log?
hi, have you figured out how to use it?
Can you please share it, thanks in advance.