Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
5 subscribers
Views
3360 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Advanced Call Web Service - Endpoint
saksheer
over 7 years ago
I 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't have the created timestamp in the correct format. The error I am getting from the service is :
com.bea.wli.sb.security.wss.WssException: java.text.ParseException: Unparseable date: "2017-01-13T11:33:17.534+0000"
Comparing with the security header that SOAP UI generates - the created timestamp is of the format : "2017-01-13T12:23:46.080Z" - which is accepted by the service.
Is there any workaround for this. Any suggestions would be appreciated!!
OriginalPostID-257599
Discussion posts and replies are publicly visible
Parents
0
saksheer
over 7 years ago
@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?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
saksheer
over 7 years ago
@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?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data