Authorization header not included in UI docs when using securitySchemes

Q&A (please complete the following information)

• OS: macOS
• Browser: Chrome
• Version: 75.0.3770.100
• Method of installation: accessed via SwaggerHub
• Swagger-UI version: unknown
• Swagger/OpenAPI version: 3.0.0

Content & configuration

Example Swagger/OpenAPI definition:

openapi: 3.0.0
info:
  version: '1.0.0'
  title: ''
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
security:
  - bearerAuth: []
paths:
  /logout:
    summary: Log out request endpoint
    post:
      responses:
        '200':
          description: 
            'OK'

Describe the bug you're encountering

To reproduce...

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

I was hoping that the use of securitySchemes above would still show that an Authorization header is required for all requests to which scheme: bearer is applied. Unfortunately this is not the case on SwaggerHub (which I assume uses SwaggerUI, but please correct me if not), where I see a padlock button that can be used to configure the auth header but no explicit textual representation.

Screenshots

Here's what I see:

Here's what I'd want to see - output as if I'd manually defined the header on each request manually, using something like:

      parameters:
        - in: header
          name: Authorization
          schema:
            type: string
          description: The JWT token
          required: true

Start by loading the supplied OpenAPI 3.0 example in Swagger UI or SwaggerHub and compare the displayed operation details with the expected Authorization header representation. Done means bearer security requirements are explicitly represented in the UI for affected requests, rather than only through the padlock control.