Multiple 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.