As referred in #289 (comment):

• Applications should avoid entirely providing securityDefinitions
• They (applications) may choose a particular definition using the schema field (globally or at form level)

This issue keeps track of how it would be possible to choose a particular scheme at the application level. One possible solution would be the definition of a proper function that lists all the possible SecurityScheme supported by a particular protocol binding and the runtime.

listSupportedSchemas(): Map<Protocol,SecuritySchemaDefinition[]>

Where Protocol could be the protocol URI scheme (i.e., HTTP,mqtt, ... )

However, I'm sure if it might have some security implications (fingerprinting?).