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

Bitwarden Enterprise: Vault Time-out policy restricts any change to 'Preferences' settings within web vault for users and admin. #9809

Open
1 task done
WinsChase opened this issue Jun 24, 2024 · 1 comment

Comments

@WinsChase
Copy link

Steps To Reproduce

  1. Enable vault time-out policy from admin web console
  2. Open user or admin web-vault that is part of a single organization
  3. Click 'Settings'
  4. Click 'Preferences'
  5. Change 'Theme' (any option)
  6. Click 'Save'
  7. Should receive no prompt of changes being saved, and see no visual change to web vault.

Expected Result

All preferences should be able to be adjusted. other than vault-time out action (Lock or Logout), and the maximum time span before locking or logging out the user.

Actual Result

Unable to change any 'Presence' settings
-Can not adjust vault Time-Out bellow or up to allowed time span set by Admin
-Can not change language setting
-Can not change Theme settings

Screenshots or Videos

No response

Additional Context

No response

Operating System

Windows

Operating System Version

Windows 11 (version 22H2)

Web Browser

Chrome, Microsoft Edge, Firefox

Browser Version

FireFox: Version 127.0 (64-bit), Chrome Version 126.0.6478.115 (Official Build) (64-bit), Edge Version 126.0.2592.68 (Official build) (64-bit)

Build Version

2024.6.1 ? access via web vault, could not find version #

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@cbbit
Copy link

cbbit commented Jun 27, 2024

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

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

No branches or pull requests

2 participants