Replies: 5 comments 2 replies
-
That is a hard "no" for me. I suggest opening up a feature request upstream to get it added to the admin page. As all other configuration is there, putting these there makes much more sense as well. ../Frenck |
Beta Was this translation helpful? Give feedback.
-
Converted this issue into a discussion, as it is not a bug. ../Frenck |
Beta Was this translation helpful? Give feedback.
-
Not sure if this is the appropriate space for this or not, but I'm posting here since it's related. Ignoring that the push notification doesn't work when I try to manually approve the pending login request I get a "We were unable to process your request." message from the Android client and this in the addon logs. I've removed the actual key and deviceIdentifier values, but I'm assuming the masterPasswordHash being null is tripping this up. I'm not sure if this is something wrong with my setup though.
|
Beta Was this translation helpful? Give feedback.
-
There seems to be no interest on the vaultwarden end in making this configurable through the admin page |
Beta Was this translation helpful? Give feedback.
-
i opend a new discussion for this topic in Vaulwarden: |
Beta Was this translation helpful? Give feedback.
-
Problem/Motivation
Now that vaultwarden supports push notifications for syncing mobile bitwarden clients, we need to be able to pass the following environment variables to the addon container enable it.
Unfortunately this cannot be done through the admin page, as the three relevant fields are in the Read Only Config section.
Proposed changes
Ideally, add the three as options in the addon configuration screen in home assistant.
Beta Was this translation helpful? Give feedback.
All reactions