Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auth: SLO: User is not logged out of Okta when selecting 'Logout of Okta' #12315

Closed
yonasberhe23 opened this issue Oct 22, 2024 · 2 comments
Closed
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@yonasberhe23
Copy link
Contributor

yonasberhe23 commented Oct 22, 2024

Setup

  • Rancher version: v2.10
  • Rancher UI Extensions:
  • Browser type & version: FF, Chrome

Describe the bug
User is not logged out of Okta when selecting "Log out of Okta". User is only logged out of Rancher.

To Reproduce

  1. as admin configure okta saml with "Allow the user to choose one of the above in an additional log out step"
  2. open user menu
  3. click logout
  4. click "Log out of Okta"

Result
User is not logged out of Okta when selecting "Log out of Okta".

Expected Result
User is logged out of Okta and Rancher when selecting "Log out of Okta".

Screenshots

Screen.Recording.2024-10-21.at.6.20.50.PM.mov

Additional context

@yonasberhe23 yonasberhe23 added this to the v2.10.0 milestone Oct 22, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Oct 22, 2024
@yonasberhe23
Copy link
Contributor Author

yonasberhe23 commented Oct 22, 2024

Found while testing #10941

@yonasberhe23
Copy link
Contributor Author

Single Logout feature was not configured in Okta. works as expected when configured.

Screen.Recording.2024-10-22.at.9.31.35.AM.mov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

2 participants