sso-proxy: internal host should apply to redeem, /refresh, /validate, /profile#123
Conversation
| Cluster string `envconfig:"CLUSTER"` | ||
| Scheme string `envconfig:"SCHEME" default:"https"` | ||
| ProviderURLString string `envconfig:"PROVIDER_URL"` | ||
| ProviderURLInternalString string `envconfig:"PROVIDER_URL_INTERNAL"` |
There was a problem hiding this comment.
I'd rather not make a breaking change here in the env-var name if possible even if we do it internally to make things clearer. if we do change things, let's make sure we update the things like the quickstart:
sso/quickstart/docker-compose.yml
Line 32 in 6db5495
There was a problem hiding this comment.
should we try to re-jigger the kubernetes quick start here
sso/quickstart/kubernetes/sso-proxy-deployment.yml
Lines 26 to 27 in 6db5495
There was a problem hiding this comment.
yep, good idea - added.
|
@benjsto thanks much for finding these. i like your solution in here neater then the one i pushed earlier. |
203aece to
979657b
Compare
…redeem, /refresh, /validate, and /profile
979657b to
ec6cd33
Compare
… internal URL for sso-auth
|
Thanks @danbf for catching that the Host header on requests to |
Problem
Dan's PR added the ability to have an optional 'internal' host defined that
proxywill use to connect toauth. However, that internal host was only applied on/redeemrequests. Other cases whereproxymakes a request toauth, like/refresh,/validate, or/profileshould also use this internal host if it is provided.Solution
If the optional
PROVIDER_URL_INTERNALis set, use that host to connect toauthfor /redeem, /refresh, /validate, and /profile.