REST API Definition not updating properly
Hello ! A few months ago we started working on a new definition for our endpoints using stoplight, but the definition went through a lot of different variations as we learned because it was one of the first ones we worked on. In ReadyAPI, I had created test plans using the first version of the definition, and then used the definition updating functionality to update my endpoints. The testing part works properly, however when I want to use the project coverage, my responses all show as 1/1 covered with no content in the message coverage window, and when I look into the "Specification" window I can see that it's not consistent with the new definition .json file. Using "definition refactoring" also does not correct the problem. Importing the definition .json file into a fresh project will create a proper service with the right specifications and unlock the ability to use project coverage, but it will be difficult to adapt transfer all the tests manually to a new service. For example, in the old updated/refactored service I would have : "responses" : { "200" : { "description" : "OK", "content" : { "application/json" : { "example" : "" } } }, } and in the freshly create service with the same definition file I would have : "responses" : { "200" : { "description" : "OK", "content" : { "application/json" : { "schema" : { "$ref" : "#/components/schemas/PlaceholderAPIBR" } } } }, } Is there a way to update the old service API with the new definition and force it to use the new response format ? The definition file also changed location and name when we started sourcing the project using Git, but I can see that the "original definition path" in the specification window and the "definition" service property are still showing the old file path. I'd rather not have to change all the tests, considering the main ReadyAPI project consume multiple services and not all of them have the issue.
Fetch Access token using OAutho0.2 - Implicit Grant
Hi, I have scenario to test ready api but that works when AccessToken is entered. So till now i have managed by entering the access token in below UI by fetching it from Access Token from UI I tried Implicit Grant but here when i click on get Access Token an UI will appear . I have written automation code in Autho Mangr-> automation code to click on Autho Selector type . But i can see it does not work at all. Here, i want to know how can i get the access token using implicit grant or is there anyother way where i can launch chrome browser and select ADFS-> Click login and ->Copy the Access token and save it into and variable and pass it into above Access Token textbox. Note - I decided to go with Implicit Grant because client is not okay to share client-ID
REST request with parameters - how to avoid default Content-Transfert-Encoding:quoted-printable ?
Hi, I am facing to an issue (with soapUI version 5.6.0). My POST REST request have two parameters. One of them is a zip file converted in Base64. In Request Raw tab You can see a parameter "Content-Transfert-Encoding" with "quoted-printable". The parameter content contains multiple lines may be due to the Content-Transfert-Encoding parameter value. Expected one line with all the parameter content How to avoid this default value ? In a previous topics one member says that soapUI uses the mail api. And explains that if the primary type of this datasource is "text", and : - If all the bytes in its input stream are US-ASCII, then the encoding is "7bit". - If more than half of the bytes are non-US-ASCII, then the encoding is "base64". - If less than half of the bytes are non-US-ASCII, then the encoding is "quoted-printable". But how to make sure that more than half of the bytes are non-US-ASCII ?
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.
Expecting claim 'qsh' to have value error message
Hello, I am trying to call endpointhttps://prod-api.zephyr4jiracloud.com/connect/public/rest/api/1.0/executionbut I am still getting 401 with message Expecting claim 'qsh' to have value 'bd5...' but instead it has the value 'b21...' I have followed documentation fromhttps://support.smartbear.com/zephyr-squad-cloud/docs/api/jwt-token.htmlwhere I first generate API keys in Zephyr in Jira, generated keys used for JWT token with attached code inside documentation and then calling aforementioned API endpoint with curl command, but still getting same think. Can you please anyone help me/explain me, what might cause this issue? Thank you in advance,
Azure Pipelines never stop with last log saying Terminate Batch (Y/N)?
I have some test pipelines in Azure that run for the maximum time allowed for the pipeline. When looking at the logs for the ready api task, I see that the last line for logging shows Terminate Batch (Y/N)? Has any one else ran into this issue. Not even sure what could be causing it when I am looking at the logs.
