Consider enhancing the filter

There’s a small section in the upstream OAS3 spec that talks about security-based filtering: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#security-filtering

It may be good for us to investigate if there’s anything the MP OpenAPI spec should say (or define) in terms of our own Filter. Should there be special treatment for Paths and PathItem, either at the filter interface or via fields / annotations?

[arthurdm]

yup, @EricWittmann has the correct idea.

With the current filter a developer needs to know two things in order to filter based on security:

• the type of security the operation has defined (in terms of OAS3 spec)
• the current user being used in the call to /openapi

The OAS3 security information should already be accessible via PathItem -> Operation -> SecurityRequirement, so perhaps one thing to investigate is making something like the javax.ws.rs.core.SecurityContext object available?

[arthurdm]

Closing this as per the concerns / comments above.