Make `x-saasify-proxy-secret` optional
amaury1093 opened this issue · 0 comments
amaury1093 commented
Right now, all requests going through this backend must have a header x-saasify-proxy-secret
set to the value of the RCH_SAASIFY_SECRET
env variable (=="reacher_dev_secret"
by default). This is used by https://reacher.email, to only allow authenticated backend-to-backend requests.
I propose to make this x-saasify-proxy-secret
check optional:
- if
RCH_SAASIFY_SECRET
env variable, then checkx-saasify-proxy-secret
header - if not, then don't check
x-saasify-proxy-secret
The idea is to make the following warp Filter optional, depending if the RCH_SAASIFY_SECRET
is set or not:
backend/src/routes/check_email/header.rs
Lines 39 to 51 in 41e46bf