Closed bharaththiruveedula-zz closed 3 years ago
The cluster's oauth-server keeps the session opened for the kubeadmin user, as would any other 3rd party SSO system hold it for their users.
The easiest way to destroy the kubeadmin's session is to go to the /oauth/token/request
page of the oauth-server, click "Display token" and then click "Logout".
HTH
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.
In case of non-kubeadmin user, I am deleting oauth-proxy, so when logged out , oauth-proxy asks for credentials. But in case of kubeadmin user even after logout, and then clicking on login button directly redirects to my homepage without asking for credentials.
I am using openshift provider