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
If thins gets too complicated because of certificate authority management, or running in development environments, we could also adopt request signature.
Both the taskworkers + brokers would have access to a shared secret.
Taskbrokers can have a list of acceptable signing secrets they accept to facilitate key rotation
When making requests, clients would generate an HMAC of the request with the signing key.
Request HMAC values are appended as gRPC headers.
Taskbroker can validate the HMAC header via a request interceptor.
The text was updated successfully, but these errors were encountered:
Longer term we may be able to use service mesh authentication, but the
requirements for that incur additional infrastructure complexity.
This level of authentication will prevent untrusted clients from
fetching and updating tasks.
Refs getsentry/taskbroker#57
)
Longer term we may be able to use service mesh authentication, but the
requirements for that incur additional infrastructure complexity. This
level of authentication will prevent untrusted clients from fetching and
updating tasks.
Refs getsentry/taskbroker#57
In production environments we need to lock down RPC endpoints with authentication so that only authorized clients can make requests.
Ideally the proxyless server mesh from GCP automatically can help us here
If thins gets too complicated because of certificate authority management, or running in development environments, we could also adopt request signature.
The text was updated successfully, but these errors were encountered: