Skip to main content
Question

How can you inter the "WSS-Type" from Soapui in HTTPCaller

  • December 4, 2017
  • 7 replies
  • 105 views

jurgenmack
Contributor
Forum|alt.badge.img+9

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?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

7 replies

jurgenmack
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • December 4, 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?

 


daveatsafe
Safer
Forum|alt.badge.img+19
  • Safer
  • December 4, 2017

Hi @jurgenmack,

The equivalent to PasswordText would be the Basic Authentication Method, when you select Use Authentication in the HTTPCaller.


jurgenmack
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • December 5, 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?


Forum|alt.badge.img

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


jurgenmack
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • December 11, 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

Hi @mdfwrestler

 

 

Have you found a way around the problem outside of FME?

 

 

 


jurgenmack
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • January 10, 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.


  • January 9, 2023

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"