[I] OpenAPIHttpSecurityScheme3_2
defines a security scheme that can be used by the operations. Supported schemes are HTTP authentication, an API key (either as a header, a cookie parameter or as a query parameter), OAuth2’s common flows (implicit, password, application and access code) as defined in RFC6749, and OpenID Connect Discovery.
https://spec.openapis.org/oas/v3.0.4.html#security-scheme-object
Extends
Section titled “Extends”Indexable
Section titled “Indexable”[key: `x-${string}`]: anyProperties
Section titled “Properties”| Property | Type | Description | Inherited from |
|---|---|---|---|
bearerFormat? | string | A hint to the client to identify how the bearer token is formatted. Bearer tokens are usually generated by an authorization server, so this information is primarily for documentation purposes. | OpenAPI3HttpSecurityScheme.bearerFormat |
deprecated? | boolean | Specifies that a security scheme is deprecated and SHOULD be transitioned out of usage. See https://spec.openapis.org/oas/v3.2.0.html#security-scheme-object | OpenAPISecuritySchemeBase3_2.deprecated |
description? | string | A short description for security scheme. CommonMark syntax MAY be used for rich text representation. | OpenAPISecuritySchemeBase3_2.description |
scheme | string | he name of the HTTP Authorization scheme to be used in the Authorization header as defined in RFC7235. | OpenAPI3HttpSecurityScheme.scheme |
type | "http" | HTTP | OpenAPI3HttpSecurityScheme.type |