Missing a receive token call in the generated client
Hello, I have the following part for securityDefinition in my swagger 2.0 API definition: securityDefinitions: petstore_auth: type: "oauth2" tokenUrl: "http://petstore.swagger.io/oauth/dialog" flow: "password" scopes: write:pets: "modify pets in your account" read:pets: "read your pets" With this API definition I generate a C# API Client with the online Swagger Editor Tool. The generated client code does not include an API call to receive the token from the given Url "http://petstore.swagger.io/oauth/dialog". What am I missing here? Thanks in advance, DavidMultiple Cookies in response for Cookie Auth
I'm working on porting an API that sets 4 cookies in it's response to a login request. Is there a recommended way to do this? I can't use Set-Cookie more than once in the headers without hitting yaml issues. I found a work-around that basically sticks a null character in front of Set-Cookie because that allows Swagger to show 4 cookies but we have open source software call connexion that flags that as invalid. I'm trying to figure out what the right approach to this would be.
intigrate access token management into auto generated swagger client
I am trying to generate my custom client using swagger definition and my own generator with some extra feature to token management and refresh token. Can I do that? We are using different gateway to connect to the rest services. There is a token management part for that gateway. So we need to integrate that token management security part into our automatically generated client. Please tell me how to do that. We are stuck at this. Please help me.
Using context parameter in Request Authorization
Hi, I am currently building a Test Case in which I use scripts to parse the response body of a few REST API Call Test Steps. 1. I create a user: POST /user/signup. 2. I log in with the created user: POST /user/login ( response body contains a JWT token that I want to use as Authorization in the following API Calls ) 3. I parse the token with the following script: import groovy.json.JsonSlurper responseContent = testRunner.testCase.getTestStepByName("POST User Login").getPropertyValue("response") jsonParser = new JsonSlurper().parseText(responseContent) context.JWTToken = jsonParser.token log.info ("Token in context: " + context.JWTToken) The token correctly logs in the log.info (line 5 of the script), so it is valid and stocked as a context variable. 4. I want to create a product: POST /products . This API Call needs a valid JWT to suceed, so I want to pass my stocked context.JWTToken as the value of the the Access Token. It doesn't work and I would gladly like to get some help on how to make it work. I also tried: ${context.JWTToken} ; context.JWTToken ; JWTToken ; ${=JWTToken} ; ${JWTToken} Thank you
Token Storage
Hi, For one of the test we wish to run we will call a service and receive a token. I am trying to understand whether when we call the service and receive the valid response with the token, whether SOAPUI stores the token somewhere, or whether a specific action needs to be taken to store the token. The token will be needed to be able to conduct subsequent test case steps? If it is not possible to store the token using a prebuilt function of SOAPUI is it possible to do this in groovy. Cheers, Tim
