Support for extensions in Security Schemes

[GiovanniCardamone]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

I am unable to add a security needed

Describe the solution you'd like

would be useful to have the extensions properti in SecuritySchemeObject in order to add extensions to the security

Teachability, documentation, adoption, migration strategy

https://swagger.io/docs/specification/v3_0/openapi-extensions/

What is the motivation / use case for changing the behavior?

would be useful when there are security that requires more than one header

[kamilmysliwiec]

Would you like to create a PR for this issue?

[mag123c]

I’m considering creating a PR to add support for extensions in the SecuritySchemeObject. My plan is to extend the schema to allow for properties like x-*, which would enable custom metadata for cases like AWS API Gateway configurations or other complex security setups.

Would this approach align with your feature request? Or do you have additional considerations I should keep in mind before proceeding with the PR?

[GiovanniCardamone]

This approach aligns perfectly for my needs, and I think it will be very useful in the scenarios you described