Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force authorize for Yarp #42

Open
fdonnet opened this issue Oct 8, 2024 · 0 comments
Open

Force authorize for Yarp #42

fdonnet opened this issue Oct 8, 2024 · 0 comments

Comments

@fdonnet
Copy link

fdonnet commented Oct 8, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant