Forum Discussion

yuanwenwu's avatar
yuanwenwu
New Contributor
14 years ago

Saml2.0 is not supported in soap UI?

I have tried several ways:

1. Paste SAML2.0 message under Outgoing WS-Security Configurations - SAML.
2. Paste SAML2.0 message in soap message header.

Either case, the SAML2.0 message is erased from the outgoing message.

Is it a bug? How to add SAML2.0 message in SoapUI if so? I have tried both soapUI Pro4.0.1 and soapUI beta4.5.1

The error in error log is:

Thu Mar 15 18:00:05 PDT 2012:ERROR:java.lang.NumberFormatException: For input string: ""
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at org.opensaml.SAMLAssertion.fromDOM(Unknown Source)
at org.opensaml.SAMLAssertion.<init>(Unknown Source)
at com.eviware.soapui.impl.wsdl.support.wss.entries.AddSAMLEntry.process(AddSAMLEntry.java:96)
at com.eviware.soapui.impl.wsdl.support.wss.OutgoingWss.processOutgoing(OutgoingWss.java:157)
at com.eviware.soapui.impl.wsdl.submit.filters.WssRequestFilter.filterWsdlRequest(WssRequestFilter.java:58)
at com.eviware.soapui.impl.wsdl.submit.filters.AbstractRequestFilter.filterAbstractHttpRequest(AbstractRequestFilter.java:37)
at com.eviware.soapui.impl.wsdl.submit.filters.AbstractRequestFilter.filterRequest(AbstractRequestFilter.java:31)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:133)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Thu Mar 15 18:00:09 PDT 2012:ERROR:java.net.ConnectException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at com.eviware.soapui.impl.wsdl.support.http.SoapUIMultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(SoapUIMultiThreadedHttpConnectionManager.java:1637)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:202)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
  • ramchalluri's avatar
    ramchalluri
    Occasional Contributor
    13 years ago
    SmartBear Support wrote:
    Actually, it's supported in soapUI 4.5.


    There are couple of issues with SAML V2 working in 4.5. I have downloaded the Community Version today and tried to get SAML (XML) working but I am not able to insert the Assertion. I can get SAML (Form) working OK but SAML (XML) is not. Can someone please tell me if I am doing something wrong. When I move my mouse over to the XML Section I am getting the following Error. 


    Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException 
      at org.fife.ui.rtextarea.FoldIndicator.findOpenFoldClosestTo(FoldIndicator.java:162)
            at org.fife.ui.rtextarea.FoldIndicator.access$300(FoldIndicator.java:60)
            at org.fife.ui.rtextarea.FoldIndicator$Listener.mouseMoved(FoldIndicator.java:671)
            at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
            at java.awt.Component.processMouseMotionEvent(Unknown Source)
            at javax.swing.JComponent.processMouseMotionEvent(Unknown Source)
            at java.awt.Component.processEvent(Unknown Source)
            at java.awt.Container.processEvent(Unknown Source)
            at java.awt.Component.dispatchEventImpl(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Window.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
            at java.awt.EventQueue.access$000(Unknown Source)
            at java.awt.EventQueue$3.run(Unknown Source)
            at java.awt.EventQueue$3.run(Unknown Source)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
            at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
            at java.awt.EventQueue$4.run(Unknown Source)
            at java.awt.EventQueue$4.run(Unknown Source)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
            at java.awt.EventQueue.dispatchEvent(Unknown Source)
            at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
            at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
            at java.awt.EventDispatchThread.run(Unknown Source)
  • DocSeuzz's avatar
    DocSeuzz
    13 years ago
    I'm not getting the error - but cannot enter any text into the SAML (XML)'s Enter SAML Assertion window. The SAML (Form) works, but doesn't allow the customization needed (which is fine). Checked the 64 and 32 bit versions of 4.5.
  • ramchalluri's avatar
    ramchalluri
    Occasional Contributor
    13 years ago
    You will get the error if you start SOAPUI with soapui.bat file instead of the exe. The error is thrown to the console not to the log file.
  • kevingann's avatar
    kevingann
    New Contributor
    13 years ago
    So it's confirmed that you have to use 4.5 to work with SAML 2.0?
  • krenevla's avatar
    krenevla
    Contributor
    13 years ago
    Hi,

    I have the same issue. Using SoapUI 4.5.1, not able to insert SAML (XML).
    Could someone from SmartBear comment on this, please?
    When I have just SAML (XML) defined in outgoing WS Security and want to insert it to request, it is not done, SAML part is empty
  • krenevla's avatar
    krenevla
    Contributor
    13 years ago
    so wss4j-1.6.7 is the cure. Replace old one in SoapUI and it will works
  • ryanvm's avatar
    ryanvm
    13 years ago
    I can verify this fix. We were seeing the same behavior trying to insert a SAML 2 assertion using the "SAML (XML)" method. Replacing the wss4j and xmlsec libraries in SoapUI with the ones from WSS4J 1.6.7 completely fixed it.

    Any chance we'll see a version 4.5.2 with this patch in the very near future? Otherwise, I have to document the process of patching the 4.5.1 installation for my users.

    Thanks!