Closed asarver closed 1 year ago
it looks like the reason the second security schema isn't showing up is because swagger is case sensitive on apikey
HeaderSchema: {
type: 'apikey',
name: 'apikey',
in: 'header'
}
it really should be apiKey
It's funny that the schema didn't catch that given it's defined here:
https://swagger.io/specification/?sbsearch=security-schemes#security-scheme-object
So should this issue be re-opened about that?
using 4.5.0
when there is a route that requires more than one security schema (using AND), the schema does not appear as an option (OR works though)