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
Description:
With current ext_authz filter implementation an external grpc_service receives only subset of request information, such as IPs and TLS details. It would be really helpful to have ability to access gRPC metadata headers as well.
Our current authorization schema is based on metadata fields added to grpc calls. Metadata is checked on server side, and we would like to move it out to Envoy filters.
It seems to be possible for http_service to configure which http headers will be passed to authz service, but nothing like that is configurable for grpc_service type.
The text was updated successfully, but these errors were encountered:
Are you sure it isn't already working? I'm finding that gRPC client-set metadata (passed as headers) gets through to our ext_authz service, appearing as regular HTTP headers. I'm using Envoy v1.14.2.
Title: Pass gRPC metadata to ext_authz
Description:
With current
ext_authz
filter implementation an externalgrpc_service
receives only subset of request information, such as IPs and TLS details. It would be really helpful to have ability to access gRPC metadata headers as well.Our current authorization schema is based on metadata fields added to grpc calls. Metadata is checked on server side, and we would like to move it out to Envoy filters.
It seems to be possible for
http_service
to configure which http headers will be passed to authz service, but nothing like that is configurable forgrpc_service
type.The text was updated successfully, but these errors were encountered: