Unable to authenticate license in Ready API Login button unresponsive
Ughhh! 3 hours wasted now. Uninstalled the latest Ready API and reinstalled. 3 days in a row now I have had to login to activate my ready api license. Today the button Login DOES NOT WORK ..so I am completely locked out of the application. The login button is completely unresponsive. No window opens to login. I am expecting a browser to open up and to login .. but nothing happens. Any suggestions / alternate paths to get authenticated?SSL Keystore Request Property not working since 3.6.2
Hello Community, up until updating to Version 3.6.2/3.6.3 i had no complications using the request property for SOAP requests "SSL Keystore". I used it either via environment properties or with the explizit configured keystore name f.e. When downgrading to 3.6.1 the client authentification works fine. With 3.6.2 and 3.6.3 ReadyAPI is not sending any client auth information to the server. So here is my question. What changed? Am i missing a new property or configuration i did not find in the update history? Best regards
Help needed with importing an API via a URL that requires a certificate for authentication.
I am trying to connect to a vendor's API (SOAP). I have a project set up and I'm trying to import their APIs. We use a certificate to connect to the site. When I go to Import API definition, it erros out saying "Received fatal alert: certificate_required" How do I use the certificate file I have in ReadyAPI? Thanks, BFasano
Response XML tab encoding
Hi, Ive got some troubles with readyAPI not correctly encoding responses in XML tab. Dont know if its some setting I have, but on similar requests Im getting different results in response XML tab. First of all I cloned whole SOAP test case (old one) and replaced old services with new ones. Here is one example of what Im dealing with. In old test case Im still getting same result in response xml tab (no matter how I run it): <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Client</faultcode> <faultstring> APP-002 : Chyba při zpracování, duplicitní údaj v požadavku (AgendaZadostId='b1e43723-54f7-447e-8d62-ed1ab98d24d7'). <!--ISZRZadostId=b1e43723-54f7-447e-8d62-ed1ab98d24d7--> </faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> <!--SERVER: TP-ISZR1APPO101--> <!--CERTIFICATEID: [3b:c6:01:57:00:02:00:00:0e:3b]--> <!--UUID: [78004a1c-6a38-1416-9628-1af38a530000], RAW:[1C4A0078386A161496281AF38A530000]--> <!--TotalTime: 00:00:00.0781195, in ms: 78.1195--> <!--DbTime (all in ms) - total: 46.8883, external: 46.8883, internal: 0, extCommit 0, intCommit 0, CWeb = 15, CWin = 0--> <!--WinService (all in ms) - total: 0, ZR: 0--> <!--Remoting: DIFF: 0 ; total: 0, winservice: 0--> <!--CodeTime: 31.2312 ; celkem: 78.1195, Proc: 39.9787505040355--> <!--OMO: 15.6112--> If I run my cloned test case with new services in test runner I get: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Client</faultcode> <faultstring>APP-002 : Chyba při zpracování, duplicitní údaj v požadavku (AgendaZadostId='02de5978-035e-4d5f-b89e-da520085aba9').<!--ISZRZadostId=c125d058-6a2f-1416-9927-173b688b1000--> </faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> <!-- SERVER: TP-ISZR1APPO101 --><!-- CERTIFICATEID: [3b:c6:01:57:00:02:00:00:0e:3b] --><!-- UUID: [4ab6460c-6a32-1416-9927-1cc57fd37000], RAW:[0C46B64A326A161499271CC57FD37000] --><!-- TotalTime: 00:00:00.0468721, in ms: 46.8721 --><!-- DbTime (all in ms) - total: 31.2513, external: 31.2513, internal: 0, extCommit 0, intCommit 0, CWeb = 15, CWin = 0 --><!-- WinService (all in ms) - total: 0, ZR: 0 --><!-- Remoting: DIFF: 0 ; total: 0, winservice: 0 --><!-- CodeTime: 15.6208 ; celkem: 46.8721, Proc: 33.3264351287866 --><!-- OMO: 0 --> And if I run this specific test step individually I also get correct response (as the old one): <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Client</faultcode> <faultstring> APP-002 : Chyba při zpracování, duplicitní údaj v požadavku (AgendaZadostId='02de5978-035e-4d5f-b89e-da520085aba9'). <!--ISZRZadostId=c125d058-6a2f-1416-9927-173b688b1000--> </faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> <!--SERVER: TP-ISZR1APPO101--> <!--CERTIFICATEID: [3b:c6:01:57:00:02:00:00:0e:3b]--> <!--UUID: [5798b974-6a5d-1416-9461-1780ea3fd000], RAW:[74B998575D6A161494611780EA3FD000]--> <!--TotalTime: 00:00:00.2499951, in ms: 249.9951--> <!--DbTime (all in ms) - total: 109.3706, external: 109.3706, internal: 0, extCommit 0, intCommit 0, CWeb = 15, CWin = 0--> <!--WinService (all in ms) - total: 0, ZR: 0--> <!--Remoting: DIFF: 0 ; total: 0, winservice: 0--> <!--CodeTime: 140.6245 ; celkem: 249.9951, Proc: 56.2509025176893--> <!--OMO: 124.9964--> Any ideas where could be the problem? As you can see the response isn't formatted as well - when I do format it after test run, everything fixes. But I don't want to do that manually, because I also need to export these responses for customer reports. Thanks for your help, M
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?
SOAP Tests aren't running after updating ReadyAPI
Hey guys, After updating from ReadyAPI 3.43 to 3.49 my SOAP tests no longer work. I was able to narrow down the problem to the outgoing WSS. It looks as if the Basic(Bultin) authentication method requires an outgoing WSS, otherwise ws-security policies do not work. After adding outgoing WSS the tests are working. Attached is the error message: HTTP/1.1 500 500 Date: Thu, 30 Nov 2023 14:05:02 GMT Server: Apache Strict-Transport-Security: max-age=31536000 Content-Type: text/xml;charset=UTF-8 X-Content-Type-Options: nosniff X-Frame-Options: sameorigin Connection: close Transfer-Encoding: chunked <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>These policy alternatives can not be satisfied: {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SupportingTokens {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}UsernameToken {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}HashPassword</faultstring></soap:Fault></soap:Body></soap:Envelope> Why is it required to add an WSS in this version, when it wasn't necessary in version 3.43? Is there a way to circumvent this WSS requirement?
How to disable "autocorrect/autofill" on SOAP requests
Using ReadyAPI to do a data driven test against a SOAP API. On each iteration, putting XML in the values for a properties test step. This is so that we can have some tests with missing elements, or other structural options. Using a placeholder in the SOAP request to grab those property values (see image). Whenever I save the project, ReadyAPI goes into my request, sees missing elements (because the placeholder puts them there during runtime) and "helps" me by shoving empty element tags in there for schema compliance. Next time I run the test, it fails because of extra tags... I have to remember to go into the request and delete the extra tags. One day I may forget and raise an embarrassing defect. Main Question: Is there a way to disable this "help" that keeps making things more complicated? (please support negative test cases - they're critical for robust testing) Thanks
