ReadyApi integration with Swagger
Hi I create Yaml file with Swagger as my Rest Api documentation and it works fine without any error and failure. But when i want to load / import it into Readyapi i receive below error: attribute.components.schema.MyAPI.default is not of type 'array' I double check in Swagger and nothing wrong, and of course the type is object , So i don't have any clue on how to solve this issue ! Does any body have similar experience ? I would be happy to share your suggestion...Solved1.2KViews0likes2Comments
SoapUI Pro 3.3.2 and Swagger 3.0.1 OAS 3.0.1
Hi, we have developed a Swaggerhub in version 3.0.1 with authentication NTLM/ https (certificate is valid). When I try to connect to swagger: 1.New project 2.Type = Swagger/ OpenAPI definition 3.URL = xxx.xxx.xxx/swagger/v1/swagger.json Prompt appears, enter valid credentials username/ password and domain. Hit enter. Same prompt appears…. I can access the endpoint directly but not through the swagger definition that has openapi: "3.0.1". I can create a new “rest step“ and with url https://xxxx.xx.xx/swagger/v1/swagger.json and get a response. But then I miss the whole idea of getting the Swagger definitions. What I can read here: https://community.smartbear.com/t5/SoapUI-Pro/Openapi-3-0-1-in-ReadyAPI-3-0-0/td-p/196697 is that it’s not supported. So could you tell me whats is going on here?Solved887Views0likes1Commentv3.0 (bug?) - swagger compliance assertion fails in v3.0 but is ok in v2.8
Hi, I recently update to v3.0 of readyAPI. Looks nice! However, I notice a difference in behavior on the Swagger Compliance Assertion. Might this be a bug at your end or is this assertion suddenly more strict in the v3.0? And if the latter, why does it flags this a failure? Scenario: Applying swagger compliance assertion to a rest response. In the assertion, I have a swagger url which contains a relative path to a yaml file. Strict validation is enabled (disabling this makes no diffrence to this issue). The validation happens and provides now these failures (note: some items are renamed for privacy reasons): 1) Instance failed to match all required schemas (matched only 0 out of 1) checked node: [/references] corresponding schema: [/properties/references] If this is a valid assertion failure then it is not a clear error message in my opinion. In my JSON response I get back the following for the reference node: Response of my usedResource: "references" : { "aReference" : "93269491-e89b-4f19-9d12-ec09b71aeaec", "bReference" : null, "cReference" : null } Is the error saying that bReference and cReference cannot be null? In my swagger/yaml file reference is defined as: usedResource: type: object description: Description of the request properties: ... references: readOnly: true description: References description allOf: - $ref: '#/definitions/ourReferences' ... ... ourReferences: type: object description: Contains the references properties: aReference: type: string description: The reference a bReference: type: string description: The reference b cReference: type: string description: The reference c 2) Instance type (string) does not match any allowed primitive type (allowed: ["object"]) checked node [/priority] corresponding schema [properties/priority] In my JSON response I get back the following for the reference node: Response of my usedResource: "priority" : "NORMAL" In my swagger/yaml file priority is defined as: usedResource: type: object description: Description of the request properties: ... priority: description: The urgency. allOf: - $ref: '#/definitions/RequestPriority' ... RequestPriority: type: string enum: - NORMAL - URGENT I cannot see what's wrong with this. Other similar nodes with similar type & enum are not resulting in a failure. Again, also v2.8 did not flag this as a failed compliance. I could provide more examples, but I hope these suffice.Solved5.8KViews0likes6CommentsHow to import Swagger definition over HTTPS behind basic authentication?
Hi, I would like to create a SoapUI NG project from a Swagger definition over HTTPS that is behind basic authentication. I'm using Ready! API 1.5.0, Swagger plugin 2.2.1. Ihave set up basic authentication in the auth repository in auth manager, but I can see in Fiddler that the credentials are not send toGET the Swagger definition. How can I use basic authentication when importing a Swagger definition? Thanks in advance! Markus2KViews0likes3CommentsHow to create SoapUI NG project from Swagger over HTTPS?
How do Icreate a SoapUI NG project from Swagger over HTTPS? I tried an see an error message An error of type SSLHandshakeException occurred. javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names present Any help is appreciated. Thanks in advance.Solved3.8KViews0likes5Comments
How to import Swagger definition over HTTPS behind basic authentication?
Hi, I would like to create a SoapUI NG project from a Swagger definition over HTTPS that is behind basic authentication. I'm using Ready! API 1.5.0, Swagger plugin 2.2.1. Ihave set up basic authentication in the auth repository in auth manager, but I can see in Fiddler that the credentials are not send toGET the Swagger definition. How can I use basic authentication when importing a Swagger definition? Thanks in advance! Markus
