components@security_schemes object

[jonthegeek]

As an API user, I'd like to create standardized API components@security_schemes objects, so that I don't have to remember the names of all the expected fields.

Make an incomplete version of components that only implements security_schemes. We'll come back for the rest later.

The scheme for this includes 4 types, which will be subclasses of a security_scheme class or something along those lines.

Be sure to sort out rules about things like security_schemes and security_scheme both being classes (that feels bad). Maybe make the top one something like security_scheme_set or security_scheme_collection ("set" has too many meanings).

Align with variables.

[jonthegeek]

Of all OAS 3.0+ specs on apis.guru, this is the breakdown of securityShemes types:

• apiKey: 1041
• oauth2: 611
• http: 194
• openIdConnect: 4

It's definitely best to start focused on apiKey!

(note that some don't have a scheme; I haven't gotten those counts yet)

[jonthegeek]

Number of securitySchemes per API:

• 0: 318
• 1: 576
• 2: 579
• 3: 27
• 4: 5
• 5: 3