OAuth 2.0 Authorization Code Grant problem
Hi there! We use SoapUI 5.7.0 and we have a problem with a code grant authorization flow. Buildin browser shows "The page could not be loaded" everytime when we try to get the app authorization form (using authorization uri parameter). We noticed that soap ui makes three requests at once: first, just GET request from authorization uri without any parameters, and then twice GET with parameters. In our case the app returns aresponce with http code 400 when we ask form without parameters and return 200 when with. Total: pushing GET ACCESS TOKEN call three requests and one of them wrong. Buildin browser show "The page could not be loaded" in this case. Is there anything we can do to fix this problem? Thanks a lot.20Views1like1CommentCreate a REST TestServer with, Get, Post, Delete, Push
Getting Started with REST Testing in SoapUI | SoapUI Hello! Do you know a good guide for a test server step by step guide. I need to access a test server from C# Desktop WPF application, query data, store data. Thanks in advance. I have no experience with the tool. There are so many settings. How do I start? Regards RobertREST 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 ?508Views0likes4CommentsSecurity 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.525Views1like5CommentsHow do I set the status of a Script Assertion?
After looking at this documentation, GroovyScriptAssertion (SoapUI 3.0.0 API) (smartbear.com), I've tried the following def currentStep = context.getCurrentStep(); def assertion = currentStep.getAssertionByName('Script Assertion'); assertion.setStatus(com.eviware.soapui.model.testsuite.Assertable.AssertionStatus.FAILED); but I get the error setStatus() exception: groovy.lang.MissingMethodException: No signature of method: com.eviware.soapui.impl.wsdl.teststeps.assertions.basic.GroovyScriptAssertion.setStatus() is applicable for argument types: (com.eviware.soapui.model.testsuite.Assertable$AssertionStatus) values: [FAILED] If I output assertion.getClass() It tells me that assertion's class is com.eviware.soapui.impl.wsdl.teststeps.assertions.basic.GroovyScriptAssertion@71d72a30 What am I doing wrong? I'm using 5.7.1 Edit: If it's not possible to set the status of a test assertion or test step, is it possible to set the status of a testCase?175Views0likes1CommentIs it possible to split up your project.xml file into lost of smaller testsuite.xml files?
We want to keep our SoapUI tests in git. However with a large team all contributing to one xml file, this is going to cause merge hell for those of us who aren't native xml parsers (ie quite a few of us). Is it possible to split up the one enormous project.xml file into lots of smaller testsuite.xml files which would still display as being part of the same project in the UI? So instead of project.xml containing myproject, testsuite1, testsuite2, testsuite3 it would be project.xml containing a reference to testsuite1.xml, testsuite2.xml, testsuite3.xml That way multiple people could be working on different test suites with no merge conflicts.386Views0likes2CommentsSwagger JSON Output
With respect to the Swagger plugin currently I am using the version like below <dependency> <groupId>io.springfox</groupId> <artifactId>springfox-swagger2</artifactId> <version>3.0.0</version> </dependency> <dependency> <groupId>io.springfox</groupId> <artifactId>springfox-swagger-ui</artifactId> <version>3.0.0</version> </dependency> in Maven project where as my Docket Configuration is as below @Bean public Docket postsApi() { return new Docket(DocumentationType.SWAGGER_2) .apiInfo(apiInfo()) .select() .apis(RequestHandlerSelectors.basePackage("com.javainuse.swaggertest")) .paths(PathSelectors.any()) .build() .pathMapping("/") .enable(true); } private ApiInfo apiInfo() { return new ApiInfoBuilder().title("JavaInUse API") .description("JavaInUse API reference for developers") .termsOfServiceUrl("http://javainuse.com").license("JavaInUse License") .licenseUrl("javainuse@gmail.com").version("1.0").build(); } and my rest API configuration is like below @ApiImplicitParam( name = "invoicedata", value = "InvoiceData data", paramType = "body", dataType = "com.javainuse.swaggertest.InvoiceData", dataTypeClass = InvoiceData.class ) @PostMapping(value = "/setSwaggerParameter") public ResponseEntity<String> setWarrantsForPendingPB(@ApiIgnore @SessionAttribute InvoiceData invoicedata) { return new ResponseEntity<String>("Ok", HttpStatus.OK); } but getting the below out in swagger like { "in": "body", "name": "invoicedata", "description": "InvoiceData data", "required": false, "schema": { "$ref": "#/definitions/ERROR - ModelName{namespace='com.javainuse.swaggertest', name='InvoiceData'}" } } Where as expecting { "in": "body", "name": "invoicedata", "description": "InvoiceData data", "required": false, "schema": { "$ref": "#/definitions/InvoiceData " } }193Views0likes0CommentsPlease help with SSL Handshake exception
Hello, I am trying to trigger a test case in soapUI 5.2.1 from command Linux , with https url and getting handshake exception. Please help if anyone aware of how to fix. Same test works from UI but failing in linux command line. 03:52:12,810 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: CONNECT env.test.gcp.com:443 HTTP/1.1 03:52:12,839 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Receiving response: HTTP/1.1 200 Connected 03:52:12,840 DEBUG [HttpClientSupport$SoapUIHttpClient] Tunnel to target created. 03:52:13,115 DEBUG [HttpClientSupport$SoapUIHttpClient] Attempt 1 to execute request 03:52:13,115 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: POST /env/bcmai/restservices/gcw/v1/mycontract/clientcontracts/ HTTP/1.1 03:52:22,839 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] I/O error closing connection javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake ============================================================= I have below options in SoapUI-5.2.1.vmoptions -Dsoapui.https.protocols=SSLv3,TLSv1.2 -Dsoapui.https.ciphers=TLS_RSA_WITH_AES_256_CBC_SHA256 -Dsun.security.ssl.allowUnsafeRenegotiation=true -Djavax.net.debug=ssl:verbose From groovy too tried enabling proxy below before running api, which didnt help. import com.eviware.soapui.impl.wsdl.support.http.ProxyUtils ProxyUtils.setProxyEnabled(true)242Views0likes0Comments