You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: versions/3.1.1.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -3917,7 +3917,7 @@ The name used for each property MUST correspond to a security scheme declared in
3917
3917
Security Requirement Objects that contain multiple schemes require that all schemes MUST be satisfied for a request to be authorized.
3918
3918
This enables support for scenarios where multiple query parameters or HTTP headers are required to convey security information.
3919
3919
3920
-
When a non-empty list of Security Requirement Objects is defined on the [OpenAPI Object](#openapi-object) or [Operation Object](#operation-object), only one of the Security Requirement Objects in the list needs to be satisfied to authorize the request; see [the `security` field](#oas-security-field).
3920
+
When a non-empty list of Security Requirement Objects is defined on the [OpenAPI Object](#openapi-object) or [Operation Object](#operation-object), only one of the Security Requirement Objects in the list needs to be satisfied to authorize the request; see [the `security` field](#the-security-field).
0 commit comments