I’ve done searches, and keep finding others with this issue, but you keep closing the request because people aren’t Voting it. That’s because the people who are experiencing this aren’t generally admins (who must have a Master Password), and therefore aren’t engaging with your community forums.
My issue is that when I want to unlock my locked account, there is no option for me to do so EXCEPT to log out completely and re-log in with SSO. That’s because I don’t have a master password set because I’m not a direct admin - I’m responsible for approvals but not administration. As such, I DON’T HAVE A MASTER PASSWORD. If I set a master password, it warns me that I will have to change my email and lose my SSO. Obviously, I don’t want to lose SSO.
I am suggesting that UNLOCK be enabled with SSO too, rather than just LOGIN. This would be a quality of life improvement for all SSO users who aren’t admins.
Again, I have seen that previously the Feature Requests that are here are closed, so I can’t upvote them - but hopefully this hits home with other users who are frustrated with the issue and are searching for answers…
Ahh, having posted, I now see I need to improve my rating before I am allowed to rate this issue - so you’re saying that you want engagement from non-admins in the forum, before they’re allowed to upvote the issue. I understand the requirements to keep the bots out, and I feel that this is understandable, but you can understand why this wasn’t clear and obvious to me - it required me to mouse over the LOCKED message to find out why my brand new Feature Request was already locked…
Okay - I’ve set a PIN and set it back to Lock instead of Log out - lets give it a go and see.
Obviously, SSO would be better, since I’m logged in to my account on the laptop, and have Passkey set up - this PIN is now not part of my external account at all, and is unique to this site… I see SSO as there to assist with the reduction of passwords/passkeys, by enforcing trust of an external entity.
This have been an issue for how long now? And what do I need to do to get to vote?
There are multiple threads requesting this simple change: Add an unlock with SSO button. Instead of confirming the request, employees and moderators are trying to divert the need into something it’s not. I DON’T want to use PIN or biometric. I just want a simple button to use SSO to unlock.
I understand that it might be more complex to implement than it seems and there are a ton of other features requested. But that don’t diminishes the wish from users.
Thank you for taking the time to reply. The voting here seems to be locked down until you’ve earned enough prestige by commenting on other things, or perhaps have been a user for a certain length of time. As mentioned, I feel that this is likely to be ‘down playing’ how important this feature is for users, because they aren’t very likely to register and post enough on this forum in order to gain that ability.
Lets hope this time, Bitwarden devs realise that from a quality of life perspective, this is a real problem for us non-admin SSO users, who don’t have a master password to use to unlock. For the record, I use Bitwarden on a personal level and a corporate one, so I do like and appreciate the quality of the product, just want this feature adding!
Please recognize that we volunteer moderators (and probably BW employees as well) are not trying to divert anything. I think I can say, mostly we are just trying to get a better understanding of a request – and often try to offer workarounds, that can “mitigate” an issue, at least until a request would be implemented.
No one did close this feature request. (and I don’t see any reason to do that)
Thanks for that feedback. Due to that, I now included “users with master password” in the title of this feature request. (@Spraggle I hope you agree to that)
Be assured, every new user (Trust Level 0) is treated equally here on the forum. The current requirements to “earn” the ability to vote are:
Please note, voting on feature requests requires Trust Level 1 (enter at least 5 topics, read at least 30 posts, and spend a total of 10 minutes reading posts).
And that is mostly a safety mechanism to prevent mass account registrations skewing feature request votes etc.
I think the reason I was saying they were closed was because it was “Locked” for voting. I misunderstood the terminology used in this forum.
Also, I certainly don’t mind the re-name of the feature request - anything that helps users find this and echo the sentiment!
<strike>On which note, I’m still not trusted enough to be able to upvote any of the feature requests - what is the requirement exactly?</strike> - answer was given above.
As far as I remember that feature request: I closed it eventually, as it was, let’s just say, not very well structured. But if you look closely, I pointed out that it had 0 votes, so nothing was lost in that regard, and I even recommended opening a new and more “straight-forward” feature request about the issue. (which only happened now thanks to @Spraggle)
So, just been struck by this again, because I have three browsers I have to use - Chrome for day to day, local edge for certain applications and AVD Edge for “VPN”. The passcode unlock work around is unique per browser and the config doesn’t carry between extensions. That makes sense only because I guess it’s hard to sync config between browser extensions.
However, it does reiterate the requirement for considering this, as the user will be impacted per browser by this limitation.
I know I sound like a stuck record, but I’m like a dog with a bone when I see things that don’t feel right.
Yes, I envision the unlock being the same as log in - I would see a “unlock with SSO” button, and single click that. Currently, there is only “Log in with Master Password” which as I don’t have one, is impossible.
You meant “Unlock with master password”, right? (because if you were logged out and have to log in again, you should already see “Login with SSO”, right?)
@Spraggle Well, to summarize again: it depends on your session timeout action if you get
logged out (–> session timeout action “Log out”)
or just locked (–> session timeout action “Lock”)
And I do see the value in staying “locked” (and therefore also logged in and just needing to “unlock”), as this retains some settings that can get lost when you log out. (like e.g. generator settings including email alias API keys)
… but apart from retaining all settings with just locking/unlocking… when “unlock with SSO” would be exact same procedure/steps as “log in with SSO”… then there would be no difference between the two (and the “log in with SSO” button already works like it would also be an “unlock with SSO” button)… or would there be a difference? (again: apart from the potential loss (with log out/log in) or retaining (with locking/unlocking) of several settings in the app/client)
To be honest, the issue for me is just being able to get in to the system with one click instead of a full sign-out then sign-in process. I appreciate that you know there is a difference between log out and locked in Bitwarden, but the end user experience for me is the same - with the exception of; if I’m logged out, I can sign back in with one button, but if I’m locked, I can’t unlock at the moment at all - because it requires a Master Password that I don’t have.
)