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

Ability to track and revoke sessions - optional enhancements #20710

Open
3 tasks
gtanzillo opened this issue Oct 20, 2020 · 0 comments
Open
3 tasks

Ability to track and revoke sessions - optional enhancements #20710

gtanzillo opened this issue Oct 20, 2020 · 0 comments

Comments

@gtanzillo
Copy link
Member

gtanzillo commented Oct 20, 2020

See original issue for full details

  • Parameterize endpoint to revoke user sessions by type manageiq-api#885 - API /api/users/ revoke_sessions action should be parameterized by type ("api", "ui", "ws", etc) and default to "all". This can be done as a follow up.

  • Log out the End-User from the OpenID Provider #20470 - Log out the End-User from the OpenID Provider

  • Update TokenManager to use Rack in place of TokenStore  #20460 - For the API, remove a majority of the custom TokenManager / TokenStore implementation and use the Rails conventions to treat a session like a token, leveraging Rack sessions. We may have to find a way to tell the Rack session classes to store the value in a different header than the cookie, so we can keep compatibility with current API header name for clients. However, the content of the token is not important to the end user, nor is it important between versions, so we can store whatever we like such as a session id.

    This might an optional for now, but without it, we will have to have duplicate implementations of 2 for each of the UI and API token managers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant