We've never provided security info in the swagger definition, what exactly are you looking/asking for?
you can't test your openapi definitions in swagger-editor or swagger-ui without defining security. See https://swagger.io/docs/specification/authentication/ . I had mentioned it in ORDS 19.1 Database API Authentication
That's it, the openapi JSON specification does not contain the security definitions used by swagger, needed to test the services that require token, using swagger-ui.
If the endpoints are unsecured, there is no problem, but if you had protected them, swagger could not be aware of that and you can not send the bearer token with your requests.
So, ORDS is not adding that required definitions, in order that I could make the API docs for third-party developers.
I'm logging an enhancement request for you, stay tuned.
It's in the swagger/openapi spec, so we could/SHOULD include it.
Hi Jeff, any news about this? Thanks!
I logged it like I said before. It hasn't been coded yet. We have about a month before 20.1 goes into feature/code freeze. So there's still a chance it'll make the cut.