-
Notifications
You must be signed in to change notification settings - Fork 5
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 #58
Comments
@guicassolato Will this change mean that tracing behaves the same as with limitador? |
It probably does, @david-martin. Thanks for pointing this out! |
@didierofrivia I guess we can close this after #92. The RFE is
The wasm-shim supports that today with the configuration action "extensions": {
"authorino": {
"type": "auth",
"endpoint": "authorino-cluster",
"failureMode": "deny",
"timeout": "5s"
}
},
...
"actions": [
{
"extension": "authorino",
"scope": "authconfig-A"
}
] Even though, the control plane does not use it (yet), this issue is completed IMO. wdyt? Can we close this?
|
Make possible for the wasm-shim to issue gRPC Envoy ext_authz requests based on configuration.
Other than the main attributes
source
,destination
, andrequest
of theCheckRequest
message, supplying values in thecontext_extensions
field must as well be supported. This will be useful to hint the authorization service lookup without the constraint on the host name as the only unique identifier of effective policies (AuthConfig CRs.)The text was updated successfully, but these errors were encountered: