https://community.appian.com/discussions/f/integrations/9581/advanced-call-web-service---endpointI am trying to call a service that uses digest auth using this smart service. Looking into the logs - the security header that the smart service generates doesn&#39;t have the created timestamp in the correct format. The error I am getting from the serviceen-USTelligent Community 12https://community.appian.com/thread/41985?ContentTypeID=1Fri, 13 Jan 2017 22:19:27 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:028b7b0e-0371-4a25-8387-224fb43b4732travisb121Maybe you could try using one of the Date Time functions to change the date time.<br /><br />Here is a link to a list of Appian Functions:<br /><br /><a href="https://forum.appian.com/suite/help/16.3/Appian_Functions.html">forum.appian.com/.../Appian_Functions.html</a><div style="clear:both;"></div>https://community.appian.com/thread/41973?ContentTypeID=1Fri, 13 Jan 2017 17:15:04 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2ed277ef-9e4f-466a-98ec-bbb3840535e6aloks0189Can you attach the screenshot of the configuration as well as flow so that we can get some idea about the issue.<div style="clear:both;"></div>https://community.appian.com/thread/41972?ContentTypeID=1Fri, 13 Jan 2017 17:02:14 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:d4db0c59-2451-4c92-95fc-3ab58d66bd20saksheer@aloks176 - Yes it is. I am working for the same service, trying to use different approaches to call it. This smart service, actually manages to go past the WSDL issues, but then again, the timestamp it generates is not accepted by the service. Any suggestions?<div style="clear:both;"></div>https://community.appian.com/thread/41971?ContentTypeID=1Fri, 13 Jan 2017 16:37:55 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:3cf6577f-466e-4fa8-b12f-8aa1f6beda86aloks0189If I am not wrong then a similar Thread is been discussed on following URL<br /><br /><a href="https://forum.appian.com/suite/tempo/entry/e-255862">forum.appian.com/.../e-255862</a><br /><div style="clear:both;"></div>