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
Under section 5.2 of the spec, it states that "If there are multiple authorization schemes described here, it means they're all applied." Is there a way to indicate that ANY instead of ALL authorization schemes are required?
Also, for the "apiKey" type, is there a way to indicate that multiple values are required? For example, 3Scale requires an app ID and app key, so you'd need two fields.
The text was updated successfully, but these errors were encountered:
Currently, there's no way to note ANY rather than ALL. If you believe that's important, feel free to open a feature request here with hopefully a detailed use-case (I can probably see the benefit, but it's better to come from an end-user of Swagger).
As for the "apiKey" - you can simply add several "apiKey" authorization schemas, one for each field. Would that satisfy the needs?
It would. But then if you add support for "ANY", I'd need a way to group them, so that they're treated as a unit (e.g. "oauth2 OR (apiKey1 AND apiKey2)").
Under section 5.2 of the spec, it states that "If there are multiple authorization schemes described here, it means they're all applied." Is there a way to indicate that ANY instead of ALL authorization schemes are required?
Also, for the "apiKey" type, is there a way to indicate that multiple values are required? For example, 3Scale requires an app ID and app key, so you'd need two fields.
The text was updated successfully, but these errors were encountered: