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
Is your feature request related to a problem? Please describe.
Hydra seems to support only following architecture.
Client -> TLS termination proxy -> hydra
Then, set TLS termination proxy's CIRDER address as HTTPS_ALLOW_TERMINATION_FROM.
But how about following case?
Client -> TLS termination proxy -> proxy -> hydra
Set TLS termination proxy's CIRDER address then it doesn't work.
Set proxy's CIRDER address then it works but is it best way?
Describe the solution you'd like
I think it's the best setting TLS termination proxy's CIDER address as HTTPS_ALLOW_TERMINATION_FROM even if there proxies between TLS termination proxy and hydra.
The text was updated successfully, but these errors were encountered:
Yes, it works but I think this is not better in the sense of HTTPS_ALLOW_TERMINATION_FROM option.
This option seems to mean "set TLS termination proxy's IP then trust it and check X-Forwarded-Proto header".
Therefore, I think it better to ensure TLS termination proxy's IP.
In addition my case, using AWS, TLS termination proxy and proxy are different subnet.
When I set HTTPS_ALLOW_TERMINATION_FROM to the IP of nginx, it works but I want to change to ALB IP.
Client -> ALB (TLS termination) -> nginx on ECS -> hydra on ECS
Is your feature request related to a problem? Please describe.
Hydra seems to support only following architecture.
Then, set TLS termination proxy's CIRDER address as
HTTPS_ALLOW_TERMINATION_FROM
.But how about following case?
Set TLS termination proxy's CIRDER address then it doesn't work.
Set proxy's CIRDER address then it works but is it best way?
Describe the solution you'd like
I think it's the best setting TLS termination proxy's CIDER address as
HTTPS_ALLOW_TERMINATION_FROM
even if there proxies between TLS termination proxy and hydra.The text was updated successfully, but these errors were encountered: