You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe I don't know how to do it but when I define security requierments (OpenId/Oauth) for the Swagger in Yarp project. It does nothing.
I m forced to define the requierements in my sub api and your ReverseProxyDocumentFilter is able to read it and propose it in the cluser I reach via Swagger (button authorize appears).
All my auth/authorization are defined in yarp via route policies. My api are open for internal accesses. So I would like to avoid a swagger auth config definition here.
Maybe it's already possible to force a specific "auth" for the Yarp project and bypass the config reading in child apis ?
For the moment, as explained, the workaround is to define the Swagger auth requierement in the api (for the authorize button to show int the Swagger Yarp) even it's not really a requierment if you can access it internally.
The text was updated successfully, but these errors were encountered:
Hi,
Thx for the job on your Swagger Yarp extension.
Maybe I don't know how to do it but when I define security requierments (OpenId/Oauth) for the Swagger in Yarp project. It does nothing.
I m forced to define the requierements in my sub api and your ReverseProxyDocumentFilter is able to read it and propose it in the cluser I reach via Swagger (button authorize appears).
All my auth/authorization are defined in yarp via route policies. My api are open for internal accesses. So I would like to avoid a swagger auth config definition here.
Maybe it's already possible to force a specific "auth" for the Yarp project and bypass the config reading in child apis ?
For the moment, as explained, the workaround is to define the Swagger auth requierement in the api (for the authorize button to show int the Swagger Yarp) even it's not really a requierment if you can access it internally.
The text was updated successfully, but these errors were encountered: