v2: Consider changing definition of OpenApiSecurityRequirement
#1974
Labels
priority:p2
Medium. Generally has a work-around and a smaller sub-set of customers is affected. SLA <=30 days
Milestone
The
OpenApiSecurityRequirement
type is currently defined asDictionary<OpenApiSecurityScheme, IList<string>>
.For v2, we should consider taking a breaking change to define it as
Dictionary<string, IList<string>>
and support referencing the security scheme by the name used in the components hierarchy in the document.The OpenAPI specification states that security requirements should an association between
{ string: string[] }
so it strikes me that we can update the type definition to align with this.This would simplify the code that users have to write when setting security requirements in documents. Instead of:
Users can write:
Is there a particular reason the object model inlines the
SecurityScheme
instead of using a name reference?The text was updated successfully, but these errors were encountered: