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
If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2
Proxy/Cert Details:
Information about the Cluster
Kubernetes version: v1.28.8+rke2r1
Cluster Type (Local/Downstream): Local
If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):
User Information
What is the role of the user logged in? Admin
If custom, define the set of permissions:
Describe the bug'
I have Keycloak OIDC enabled for authentication to Rancher from Keycloak. When I logout from rancher and then again try to login it does not ask for credentials(Session does not get invalidated).
To Reproduce
Configure Keycloak OIDC in Rancher.
Login to Rancher
Logout from Rancher.
Retry to login to rancher. it would not ask for credentials.
Result
Upon logout user session is not invalidated.
Expected Result
Upon logout it should invalidate the session and re-login it should validte the credentials of the userr
The text was updated successfully, but these errors were encountered:
Correct, that means a logout from Rancher is not a logout from Keycloak. So we have here a "normal SSO behavior", when there is no option to configure a logout url ... as its done for rancher.
I think you should request this as "Feature" for configure a logout url. As I said, its not a bug.
Normally you can also logout of keycloak, then you are logged out of rancher also. Thats working fine
Rancher Server Setup
Information about the Cluster
User Information
Describe the bug'
I have Keycloak OIDC enabled for authentication to Rancher from Keycloak. When I logout from rancher and then again try to login it does not ask for credentials(Session does not get invalidated).
To Reproduce
Result
Upon logout user session is not invalidated.
Expected Result
Upon logout it should invalidate the session and re-login it should validte the credentials of the userr
The text was updated successfully, but these errors were encountered: