-
Notifications
You must be signed in to change notification settings - Fork 27
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
Cannot save new login if personal ownership is disabled #1874
Comments
Just found this here. An issue was discovered when Single Organization & Remove Individual Vault options were turned on for an organization. We reported an issue with the browser extension here: https://github.com/bitwarden/clients/pull/4808. I have also determined that same user when using iOS Safari browser attempting to save a new item, when they use the share sheet they do not have any access to any collections. When they save the item they just get a spinning circle and "saving." I believe the problem is due to them not having the ability to choose which collection to save the item to. If they exit out and go into the Bitwarden iOS app, they are able to save the item there since they are able to choose which collection to save the item to. @oglodyte has created this more than a year and half ago and still hasn't been fix. |
Does anyone need more of a step by step breakdown to replicate this? Is there not enough information provided to reproduce? I’m looking to do whatever I can to have this resolved. If this can’t be reproduced please advise and maybe a better explanation can be provided. |
if you can reproduce this, can you at least put this on the teams radar. I have a feeling this hasn’t been looked at..at all but I can surely reproduce. Additionally there was some work similar to this setup, done on the browser extension side. |
Hi everyone, Thank you for your reports. I was able to reproduce this behaviour and I have flagged it to our Engineering team. If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them. Thank you again, |
@SergeantConfused is this on their list to fix? Any expectation of when this would start being worked on , this year ? 2024? 2025? Thank you |
Any update on this??? |
@SergeantConfused is this moving along???? |
@bitwarden-devops-bot any update? |
@djsmith85 any update on this? |
I just lost 2 organizational clients due to this. |
Hello all, this item has been resolved in the new native apps. These apps are currently in open beta, and will be generally available soon. |
@micahblut is this still a work in progress? I just tested this on the native app and we receive an error stating due to an organizational policy you cannot save to personal vault. We don't have personal vault turned on since personal ownership is disabled. |
@Gerardv514 can you clarify which of the native apps you are testing on? When I test this flow, I see a message at the top of the item creation form informing me that an organization policy affects my ownership options. When I try to save without selecting a collection, I see a message that I need to select a collection. When I select a collection and save, the item is saved. RPReplay_Final1721633930.MP4 |
Testing in iOS iPhone 14 Pro native app 2024.7.0 (1194). Looking at your video, is that iOS? It appears very different. |
Yes, this is iOS. Here are instructions for getting the iOS beta: https://community.bitwarden.com/t/about-the-beta-program/39185 Perhaps it looks different because I'm using dark mode? |
Steps To Reproduce
Expected Result
Login saved
Actual Result
Extension hands on saving new login
New login is not saved
Screenshots or Videos
No response
Additional Context
Extension does not offer to set the collection for the new login and it is mandatory when personal ownership is disabled.
Proposed Solution(s):
Operating System
iOS
Operating System Version
15.4.1
Device
iPhone 13 Pro Max
Build Version
12.17.0 (1626)
Beta
The text was updated successfully, but these errors were encountered: