Hide Forgot
Description of problem: When a user's password is changed, all active sessions/activity that a user has on the Satellite remain active. This causes a concern for when a user is terminated from their organization and needs to have their access revoked immediately. It should be possible to immediately stop all sessions/activity upon a password change. Version-Release number of selected component (if applicable): 6.3.2 How reproducible: Always Steps to Reproduce: 1. Have a user login to the satellite and start doing things. 2. Have an admin change the users password. 3. Actual results: The user remains logged in and activity they have started remains active. Expected results: User is immediately logged out and their activity is stopped. Additional info:
If you need to have user access revoked, you need to remove the user account. Changing password seems like some workaround. That would even be impossible for users with external auth source. Also that wouldn't invalidated API tokens that could still be used. Note that even after account deletion, all audits remains untouched if some later investigation of user activity is needed. What prevents customer from simply removing the user account? Would that solve this case?
From customer: "In this specific instance we don't want to have to remove the user. I still feel that the change of a password should invalidate active sessions. I don't find much from google in terms or best practice around this, but certainly one educational / beginners guide for rails and user management does just this." Cheers, Karl
Created redmine issue https://projects.theforeman.org/issues/28342 from this bug
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you