Advanced Call Web Service

There is no explicit limit configured at this time, however it's recommended to keep payloads a sensible size and in-line with other native integration options of the platform (see WebAPI and Integration Object documentation for their limits and aim to use this plug-in in-line with those)

The Service Authentication section in the documentation lists the following supported authentication methods:

• USERNAME_TOKEN_DIGEST_PASSWORD
• USERNAME_TOKEN_PLAIN_PASSWORD
• USERNAME_TOKEN_NO_PASSWORD

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

• Fixed issue with Exception bundle

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.