From a349e30aa20d2fa851afe6cd041e05eb4b1b8a26 Mon Sep 17 00:00:00 2001
From: Phil Sturgeon <me@philsturgeon.com>
Date: Thu, 3 Jun 2021 21:02:27 +0100
Subject: [PATCH] Let Security Schemes declare deprecation

---
 versions/3.2.0.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/versions/3.2.0.md b/versions/3.2.0.md
index 87a88906b2..6b33bc17cf 100644
--- a/versions/3.2.0.md
+++ b/versions/3.2.0.md
@@ -3202,6 +3202,7 @@ Field Name | Type | Applies To | Description
 <a name="securitySchemeBearerFormat"></a>bearerFormat | `string` | `http` (`"bearer"`) | 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.
 <a name="securitySchemeFlows"></a>flows | [OAuth Flows Object](#oauthFlowsObject) | `oauth2` | **REQUIRED**. An object containing configuration information for the flow types supported.
 <a name="securitySchemeOpenIdConnectUrl"></a>openIdConnectUrl | `string` | `openIdConnect` | **REQUIRED**. OpenId Connect URL to discover OAuth2 configuration values. This MUST be in the form of a URL. The OpenID Connect standard requires the use of TLS.
+<a name="securitySchemeDeprecated"></a>deprecated | `boolean` | Declares this security scheme to be deprecated. Consumers SHOULD refrain from usage of the declared scheme. Default value is `false`.
 
 This object MAY be extended with [Specification Extensions](#specificationExtensions).