I am trying to access a SOAP service that is password protected. In Soapui I had to set the WSS-Type to PasswordText in order to get the result I wanted. How can I duplicate this in FME desktop?
How can you inter the "WSS-Type" from Soapui in HTTPCaller
+6
- Contributor
- 31 replies
-
4 December 2017
"Enter not inter"
When I run the workbench I receive a http 500 error. This occurred with SoapUI until I set the WSS-Type = PasswordText
Is there a field or attribute in the HTTPCaller that I can set?
Userlevel 2
+17
- Safer
- 1580 replies
-
4 December 2017
Hi @jurgenmack,
The equivalent to PasswordText would be the Basic Authentication Method, when you select Use Authentication in the HTTPCaller.
+6
- Contributor
- 31 replies
-
5 December 2017
@DaveAtSafe
It looks more like a ssl error. When I select yes for verify ssl certificates, I receive a "SSL connect error"
When I select no for verify ssl certificates, I receive a "http/1.1 500 internal server error"
I have confirmed the settings on SoapUI and set them the same in FME.
Any ideas?
Hi jurgenmack/Dave
Just to add I too have exactly the same issue.
Basic Authentication + Yes to verify ssl certificates and I receive a "http/1.1 500 internal server.
Having trawled the Knowledge Base I came across this post suggesting FME cannot handle SOAP ssl certificates - it's not up to the job!
https://knowledge.safe.com/questions/31624/soap-ws-security.html
+6
- Contributor
- 31 replies
-
11 December 2017
Hi jurgenmack/Dave
Just to add I too have exactly the same issue.
Basic Authentication + Yes to verify ssl certificates and I receive a "http/1.1 500 internal server.
Having trawled the Knowledge Base I came across this post suggesting FME cannot handle SOAP ssl certificates - it's not up to the job!
https://knowledge.safe.com/questions/31624/soap-ws-security.html
Have you found a way around the problem outside of FME?
+6
- Contributor
- 31 replies
-
10 January 2018
If the WSS-Type is other than blank you have to provide that information via the XML Templater Transformer. I still left the basic authentication information in the HTTP-Caller but the Templater did all the work. After a successful connection with soapui you will have the soapenv:header>wsse:security line. Add this above your soapenv:body in your templater.
If the WSS-Type is other than blank you have to provide that information via the XML Templater Transformer. I still left the basic authentication information in the HTTP-Caller but the Templater did all the work. After a successful connection with soapui you will have the soapenv:header>wsse:security line. Add this above your soapenv:body in your templater.
How did it work with you? I copied the header information from SoapUI and it included a timestamp, it worked the first time but sending the same timestamp gave me the below error:
An error was discovered processing the <wsse:Security> header (An error happened processing a Username Token "A replay attack has been detected"
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.