securitySchemes - Semantic error - Security requirements must match a security definition

• Swagger/OpenAPI version: OpenAPI 3.0.1

Example Swagger/OpenAPI definition:

components:
  securitySchemes:
    OAuth2q:
      type: "oauth2"
      flows:
        clientCredentials:
          tokenUrl: "https://api-test.XXXXX.com/oauth/token"
          scopes: {}

Describe the bug you're encountering

• We are required to create 2 securitySchemes for an OAuth2 clientCredentials
• Swagger UI only allow one OAuth2 name
• securitySchemes name is case-sensitive
• securitySchemes will not allow duplicate name
• The same behavior when tested in https://editor.swagger.io/
• We isolated the issue by just using one invalid name (ex: OAuth2q)

Screenshots

Additional context or thoughts

Screenshot when trying to remove the arbitrary name:

Start by reproducing the reported behavior in Swagger UI and editor.swagger.io with the supplied OpenAPI 3.0.1 securitySchemes example, including the OAuth2q name. Trace how the security requirement is matched to the security definition; done means the valid case is accepted without requiring duplicate schemes and the invalid-name behavior is clearly defined.