Advanced Call Web Service

Hi!,

I have the same question. Is it possible to make it compatible?

Thanks!

Hi!

Is it possible to make this compatible with Appian 21.3? (given the base product's removal of TLS1 and TLS1.1 protocols)

Thanks!

Hi,

In Appian cloud environment  Im using the advanced web service call and the web service end-point WSDL and XSD imports were failing to load due to some network  infrastructure issues.   

I had to resort to  using Appian OOTB Call Web Service smart service in test process model to isolate root cause analysis because all the advanced web service code is just logging off the root message from exception call stack which results in generic "HTTP transport error: java.net.ConnectException: Connection timed out" message.   For reference we had to use this plugin because web service WSDL / message definitions contain unsupported XSD schema types so we are hand building the XML message requests

For future support issue trouble shooting I was wondering if anyone knows where in Appian cloud environments the full exception stack might already be logged (I didn't see anything in  tomcat std out log file) or if there is some log configuration changes which I can request of  cloud support team to get them captured.

Thanks.

Bob 

Hi, 

Has anyone used the advanced service endpoint smart service where ssl/certifcates are required?   In a cloud Appian environment do I just use the admin console certificates feature  to import certificate or us keystoreDocument & keystoreSystemKey service authentication inputs required.  If latter am I understanding documentation correctly that I need to create a key store with certificate and upload as document to appian cloud environment?

Thanks.   

hello,

is there a way to define a custom content-type for soap attachments? This plugins uses application/octet-stream by default, but I need to change it in application/pdf.
Thanks in advance for your time and for support.

Best regards

Stefano

'Manually' setting the data for HTTP Basic Authorization in the HTTP Headers input worked. For some reason, I still have to set 'USERNAME_TOKEN_PLAIN_PASSWORD' and use a key otherwise I get a java runtime exception (  java.lang.RuntimeException: Invalid username token configuration provided' ), but it is at least a working solution until something better is found.
Thank you for the support.

Yes, this is HTTP Basic Authentication.

Ok, understood, the plugin does not explicitly support this feature. Will try sending it in headers as per your suggestion.

The authentication actions in this plug-in are specifically designed to work with WS-Security UsernameToken profile. Which is different to what I believe you're asking for (HTTP Basic Authentication). This one which uses the "Authorization" HTTP header to encode and send the credentials.

As this plug-in allows HTTP Headers to be se, it may be possible to pass the Authorization header however this would bypass the Third Party Credential store which is needed to securely and safely manage credentials.

Hi,
Trying to use the plugin to make a call to a service with simple authentication. I repeatedly receive 401 error. The key is configured in the third party credentials store ( 'username', 'password' ) and the values for them as far as I can see are correct, and in the 'Service Authentication' input of the smart service the '={ action: "USERNAME_TOKEN_PLAIN_PASSWORD, usernameTokenSystemKey: <name of key in store> }" value is set.

 - Is there any way to see  the full request body without making Appian environment changes ?
 - Is there a way to send the credentials without resorting to third party credentials feature ?

Thank you,

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)