Problem with authentication about ktor-openapi-generator

[Wicpar]

it's possible there was a regression

[RamsesGomez]

Any suggestion? An idea of what should we change?

[Wicpar]

do you have an implementation I can test to reproduce ?

[RamsesGomez]

when you said "It's possible there was a regression" what do you really mean by this? We are following the exact same example you have with the exception that we have both unauthorized routes and authorized ones.
Maybe that helps. Unfortunately I do not have an implementation for you to test.

[Wicpar]

can you send the openapi.json ?
Have you tried the openapi.json on Redoc, it is has a better implementation of the standard.
A commit between *.14 and *.18 changed the definition as it was not coherent with the standard.
The regression would be in the library, as a few PRs have been accepted since.

[Wicpar]

@RamsesGomez I just tested the JWT test and it has the authorization as expected... I did update a few libraries though, let me wrap that up so you can try.

[Wicpar]

@RamsesGomez try the latest release and tell me if it works

[RamsesGomez]

@Wicpar Awesome let me try thanks a lot for the swift response

[RamsesGomez]

I tested it but no luck I can see that the new generated json looks like this:

"security": [ { "entries": [ null ], "keys": [ "jwtAuth" ], "size": 1, "values": [ [ "Dummy" ] ] } ],

where as the old one looked like this:

"security": [ { "jwtAuth": [ "Dummy" ] } ],

[RamsesGomez]

You mentioned you have an example that worked is it possible to see that sample?

[RamsesGomez]

Ok We found the problem... we have a custom serialization module to be able to use kotlin serialization, and the SecurityModel now is a Map and that was the problem, all DataModel were being serialized differently but now is all good thanks a lot for the support much appreciated