Authorization header on OAS3 specification not present. #25
Description
We have noticed that when loading a Swagger 2.0 specification, the authorization header (lock) button on top of the page is present and seems to work normally. However when loading a OAS 3.0 specification that is not present. Is that something that is known to be missing? If so, any plans to add it soon?
We understand that security definitions are only at 25%, so it seems reasonable for it to not be working. That said, great job so far! It looks really good.