Closed samuelvl closed 2 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
Description I am working on this scenario to have a full SSO experience:
If I login in the
app1
I don't want to relogin again inapp2
. So I am using the--cookie-domain
flag to enable the cookie in all the applications of my domain:However when I am already logged in
app1
and try to reachapp2
I am getting the following error:I have been digging into the code and I realized the cookie signature is including the route hostname even if the
--cokie-domain
flag is set:https://github.com/openshift/oauth-proxy/blob/d347e1a29cdc5214ef9d15d61c328fbc24340192/oauthproxy.go#L411