Add security schemes and requirements to generated OpenAPI spec #620
Labels
needs-kind
Indicates an issue or PR lacks a `kind/foo` label and requires one.
needs-priority
Indicates an issue or PR lacks a `priority/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
In order for autogenerated OpenAPI clients to be able to authenticate with the Hub, we need to specify the security scheme and requirements in our OpenAPI spec. Swagger/OpenAPI2 does not appear to have a
bearer
auth type, so our current process of generating OpenAPI2 and then converting it to OpenAPI3 will likely not work here.The text was updated successfully, but these errors were encountered: