Skip to content

Add security schemes and requirements to generated OpenAPI spec #620

@mansam

Description

@mansam

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-kindIndicates an issue or PR lacks a `kind/foo` label and requires one.needs-priorityIndicates an issue or PR lacks a `priority/foo` label and requires one.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.stale

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions