I am using bitwarden/vaultwarden in my family and we are lacking the ability to configure shorter emergency access wait times (e.g. phone of family member is stolen during vacation, etc.)
Currently the shortest time that can be configure is 1 day.
I am proposing to offer the ability to choose a couple of hours (or even no wait time). In LastPass this is for example possible.
Is there any plan to implement this in Vaultwarden?
Thanks in advance!
@FabiB98 Welcome to the forum!
I moved your post into an existing feature request on the same topic.
I would like to note, that this is the Bitwarden Community Forum. Bitwarden is not associated with Vaultwarden in any way – and if you have any questions regarding Vaultwarden, then please seek assistance in their community spaces.
This is because the wait time is stored in a variable WaitTimeDays that is an integer type (representing the number of days to wait). Changing the back-end to accommodate floating point values <1, or to change the variable to WaitTimeHours will require significant modifications of the server software. Thus, the Vaultwarden devs would need to be on board with implementing this feature, and you would have to file a request with them.
I see the problem! But seeing the long discussion above, it would be anyways worth to think about this.
I already asked this in the Vaultwarden community, but they said it would be a bitwarden topic….
Best regards
I don’t think that the person who responded to you (@Gerardv514) in that issue is a Vaultwarden (or Bitwarden) developer. Did you close the issue yourself after that comment?
To be fair, there would have to be changes made on both the client side (Bitwarden) and the server side (Vaultwarden) to make this happen — but the major changes would be on the server side. @dani does development for both Vaultwarden and Bitwarden now, so your best bet would be to get him on board with starting a PR…
Essentially it would have to be developed first by Bitwarden since that is an upstream project. And then yes Vaultwarden would make it compatible for their server. Bitwarden first because they also maintain the clients and maybe clients need to have this feature developed too. If Vaultwarden makes the change but the Bitwarden clients haven’t it wouldn’t work. So ultimately main project changes should happen upstream first. And yes sometimes it depends what the change is, to know if it should be directed to Vaultwarden only.
@FabiB98 @Gerardv514 As this side discussion was mainly about Vaultwarden – and not relevant for the feature request itself – I now moved our posts into this separate thread.
This topic was automatically closed after 7 days. New replies are no longer allowed.