WS-Security Configuration XML Code
The SOAP API I am trying to connect with requires a Outgoing WS-Security Configuration which i created and added an element "fooBar". It had the following components: Username Password Add Nonce (checked) Add Created (checked) Password Type : PasswordText This was all added into the SOAPUI Project and configured and Assigned into the ServicesSoapBinding Service Endpoints in the Outgoing WSS column for the SOAP API Endpoint. The service runs successfully and returns the data. But when I look at the Raw XML I do not see the XML code generated for this configuration. This causes an issue when trying to create the API call in my code (VS.net) I do see a usernameToken: <wsse:UsernameToken wsu:Id="UsernameToken-1A2345BC79125763217146873325036"> <wsse:Username>fooBar</wsse:Username> I do not see how that UsernameToken is generated and when I create my UsernameToken it is in the form of a GUID not Hexadecimal This is the RAW XML generated for a successful call: POST https://Host SOAP API URL HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: text/xml;charset=UTF-8 SOAPAction: "API Method" Content-Length: 1068 Host: Host Domain Connection: Keep-Alive User-Agent: Apache-HttpClient/4.5.5 (Java/16.0.2) <soapenv:Envelope xmlns:ejb="https://Host SOAP API URL" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss- wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-1A2345BC79125763217146873325036"> (dummy token) <wsse:Username>fooBar</wsse:Username> (Raw XML included the name of the WS-Security Configuration element not the actual password) <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">Password</wsse:Password> <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">Password encryption</wsse:Nonce> <wsu:Created>2024-05-02T22:02:12.503Z</wsu:Created> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <ejb:API Method> <vendorId>Real Password</vendorId> <applicationId>Real AppID</applicationId> </ejb:API Method> </soapenv:Body> </soapenv:Envelope> Is there a way to see the missing generated WS-Security Configuration code? Thanks.Gradle publish not working suddenly from today.
Could not resolve all artifacts for configuration ':classpath'. > Could not resolve io.freefair.gradle:aspectj-plugin:3.8.4. Required by: project : > Could not resolve io.freefair.gradle:aspectj-plugin:3.8.4. > Could not get resource 'http://smartbearsoftware.com/repository/maven2/io/freefair/gradle/aspectj-plugin/3.8.4/aspectj-plugin-3.8.4.pom'. > Could not HEAD 'https://rapi.tools.ops.smartbear.io/nexus/content/groups/public/io/freefair/gradle/aspectj-plugin/3.8.4/aspectj-plugin-3.8.4.pom'. > Read timed out Could you please let us know the reason. Regards, Raghavender.
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!
In Ready API Tool - Not able to Add sections in Request -> Form (Tab)
I have added a new field in the API request but not able to add the new feild details in the Request -> Form (Tab) all the sections are disabled as per the screen shot. Can someone help me on how to add the new section to add the new fields in the Request -> Form (Tab)? Also, in the API request View Type -> All is selected from dropdown but still the data is viewed as clutter sections and feild details not able to see section and fields in the proper form (as per attached screen print) . How to resolve this issue?
