How to upload a file via SOAP, as an attachment using python zeep
Hi folks, I am trying to attach a log.txt file with my createAttachment web service. I am using zeep as a client to do so but unable to do. I tried the same using MIME but unable to do so. import requests url = "WSDL url" payload = '''<?xml version="1.0" encoding="utf-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.ca.com/UnicenterServicePlus/ServiceDesk"> <soapenv:Header/> <soapenv:Body> <ser:createAttachment> <sid>'''+sid+'''</sid> <repositoryHandle>doc:12</repositoryHandle> <objectHandle>cr:1306599</objectHandle> <description>Testing to attach document to change order</description> <fileName>log</fileName> </ser:createAttachment> </soapenv:Body> </soapenv:Envelope>''' files=[ ('fileName',('Testing.txt',open('C:/Users/prasaka/Desktop/Testing.txt','rb'),'text/xml')) ] headers = { 'Content-Type': 'text/xml; charset=utf-8', 'soapAction': 'application/soap+xml' } response = requests.request("POST", url, headers=headers, data={'data' : payload}, files=files) print(response.text) print(response.status_code)
Support for java 17 using SoapUI-maven-plugin.
Hi! Can you please tell me how could it be possible to use SoapUI-maven-plugin with java 17? I would like to use it on Jenkins, and I cannot install java 16 in Jenkins... because it runs on AWS and all my other tests (Selenium) are running on Java 17. While I tried in maven to use maven-compiler-plugin with release version 16, it throws an error that a groovy script cannot be run because of unsupported class file major version 61. On my local SoapUI works as expected with java 17, but the soap plugin no.
How to reproduce this message signature in code
Hi guys, I have had a tough time solving this puzzle, according to the above configuration SoapUI should sign the whole message as described in the documentation here Unfortunately, this description doesn't align with the SignedInfo node in the soap message, where it appears to sign only the message body, as apparent from the Reference tag and Id pointing to the body Id. I tried doing it with different combinations without any luck. If I sign only the message body the digest and Signature value don't match with that of SoapUI. Then I also tried signing the whole soap envelope but that too doesn't work. Even if it is the whole message, which parts does it include, like the Headers, Binary Security Token, TimeStamp and body or only the TimeStamp and body. The digest changes with every request. I hope someone also got this issue and found a way out, if yes please let me know. Thank you!
Security configuration for SOAP project using two way SSL with client certificate for auth
Hello Community, I am struggling with configuration of my SOAP project to use client certificate in two way SSL encryption tunnel. I tryied both these guides: -https://www.soapui.org/docs/soapui-projects/ws-security/ -https://www.soapui.org/docs/security-testing/ws-security-settings/ But unfortunatelly I cannot connect to the server. When I use CURL with cert and key it is working like a charm: curl --request GET --url https://XXXX/service1\?WSDL --cert cert.pem--key key.pem OR curl --request POST --url https://XXXX/service1 --cert cert.pem--key key.pem --header 'Content-Type: text/xml' --verbose -d @request.xml However when I create JKS trustore with both of them and I add it to SoapUI, according those guides, I am getting unauthorized response all the time. I tried it on Windows10 and Ubuntu22.04 with SoapUI 5.7.1 Could you please give me nudge or hint how should I configure the SoapUI project to authenticate using 2 way SSL? Thank you.Failed to update interface when updating wsdl definition
Hi. I am using SoapUI Open Source v5.6.0. When I update a wsdl, the error ‘Failed to update interface: [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException]’ is being returned. Looking at the error log: Thu Jan 11 09:19:26 EST 2024:ERROR:com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlInterfaceDefinition.load(WsdlInterfaceDefinition.java:52) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinition(WsdlContext.java:62) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinition(WsdlContext.java:34) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.cacheDefinition(AbstractDefinitionContext.java:245) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.access$400(AbstractDefinitionContext.java:47) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:218) at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46) at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:131) at java.base/java.lang.Thread.run(Thread.java:835) Other people in my office using SoapUI are not having an issue with this wsdl. I am not sure if this is related, but the environment recently had its’ Tomcat version updated, and I was testing with this wsdl before the update. When I try to create a new request, I am just getting the envelope, header, body and endpoint name. None of the definition. When I use the ‘Recreate a default request from the schema’ icon, I am getting the same skeleton request. Any ideas? Thank you. Angie
