The Advanced Call Web Service provides support for the following:
The attachment provided with the download provides more information and examples. Where possible, use the base product Call Web Service functionality instead.
While trying to access a URL via API, i am getting a status code of 301. When i try to access the same via a browser using the developer tools, i am getting a status code of 200 meaning its a success. Can i please get some suggestions on the same?
Per plugin documentation, you should be able to specify the "sslProtocol" property to use TLSv1.2.
I have the same question. Is it possible to make it compatible?
Is it possible to make this compatible with Appian 21.3? (given the base product's removal of TLS1 and TLS1.1 protocols)
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.
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?
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.
'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.
© 2022 Appian. All rights reserved.