-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
ext_authz is ignored for paths matching a grpc_json_transcoder filter #9929
Comments
I found that if I add a third route: - match: {prefix: "/" }
route: { cluster: samlauth } then everything works properly. Smells like a bug! |
cc @dio |
your problem is this line:
because the grpc filter changes the path header and clears the route cache, route selection will be done after the ext auth filter; |
If you reverse the order of the filters, it kind-of works. My ext_authz service returns an empty body, a location header, and a 307 status code. When I reverse the order and omit the third route (mentioned here), I get the correct location header, a 500 status code, and a non-empty body (grpc error as json) |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions. |
(as of v1.13.0)
Having trouble hiding a grpc_json transcoded server behind ext_authz. With the below config, any valid
guinanpb/Guinan
endpoint skips over ext_authz.If I rearrange the filters (grpc_json before authz) the authz check occurs, but envoy always returns a 500 error code (my service redirects for SAML auth)
The text was updated successfully, but these errors were encountered: