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

Testing of Session Time out #5381

Closed
kalroy opened this issue Jul 27, 2021 · 1 comment
Closed

Testing of Session Time out #5381

kalroy opened this issue Jul 27, 2021 · 1 comment
Assignees
Labels

Comments

@kalroy
Copy link
Collaborator

kalroy commented Jul 27, 2021

Things Introduced.

  • Automate UI checks for user activities such as mouse movement, click, keyboard key press, scroll etc.
  • If there is no activity from user's side for the time specified for idle_timeout_minutes in config.toml then user will be
    explicitly logged out.
  • This feature can be enabled/disabled by enable_idle_timeout this property in config.toml
  • User kept multiple tabs/windows open but active on any one of the tab/window, to accommodate this use-case, such that user is not logged out as user is active. (https://github.com/pubkey/broadcast-channel) is used, It supports all browsers.

👟 How to Build and Test the Change

  • Pull changes from branch abdul/ui_timeout_fix

  • update session.toml to desired values.
    125940193-a6fb8a2f-3e79-4e60-b8df-d7839a0b855f.png

  • cd /src

  • rebuild components/automate-load-balance

  • rebuild components/automate-ui

  • rebuild components/automate-deployment

  • rebuild components/automate-cli

  • chef-automate config patch dev/session.toml

Things to Test

  1. Check if user is logged out after specified idle_timeout_minutes provided enable_idle_timeout is set to true and user is idle (mouse, keyboard, scroll) activities shouldn’t happen.
  2. Same way set enable_idle_timeout to false and check user shouldn't get logged out in idle scenario.
  3. Test idle scenario in with different tabs/windows of automate ui open in logged in state, keep any one tab active user shouldn’t get logged out.
  4. Above 3 steps should be valid for Local User, SAML and LDAP logins.
  5. Check for cross-browser compatibility

Definition of Done

Aha! Link: https://chef.aha.io/epics/SH-E-724

@kalroy kalroy changed the title Testing of Session Time out and Authentication Improvement Testing of Session Time out Jul 27, 2021
@kalroy kalroy added the Team: Kinetic Analysis, user managerment, compliance size, govt findings, Telemetry, Customer bugs, CVE issues label Aug 4, 2021
@sonali523
Copy link
Contributor

Testing observations:
Google Chrome 92.0.4515.107 (Official Build) (64-bit)

  1. For a single tab for both local and LDAP, User is logged out after specified idle_timeout_minutes provided enable_idle_timeout is set to true and user is idle (mouse, keyboard, scroll) activities are not happened.
  2. For a multiple tabs,
    a) Local user: User is logged out from all the tabs only after specified idle_timeout_minutes provided enable_idle_timeout is set to true and user is idle (mouse, keyboard, scroll) activities are not happened.
    b) LDAP:
    - If user is logged into multiple tabs , and user is inactive on one tab for 2 minutes then other tabs are logged out before the idle_timeout_minutes, if specified idle_timeout_minutes is 3 minutes and enable_idle_timeout is set to true
    - If user is logged into multiple tabs, then user is logged out from all the tabs only after specified idle_timeout_minutes is of 5 minutes provided enable_idle_timeout is set to true and user is idle (mouse, keyboard, scroll) activities are not happened.(For the Minimum 5 minutes it working fine)

@kalroy kalroy closed this as completed Aug 17, 2021
@AnkurMundhra AnkurMundhra added Epic and removed acceptance: verified Team: Kinetic Analysis, user managerment, compliance size, govt findings, Telemetry, Customer bugs, CVE issues labels Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants