You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that Vaultwarden does not support CXP (credential exchange protocol) for import/export, and sent out #6853 for adding the client side feature flags.
During the investigation, I noticed that there are many Bitwarden feature flags that are not available on vaultwarden. Most of the feature flags seem to require nothing but pass a map entry of key:"true" in the api config.
I'm wondering, as a popular self-hosting solution, is there a reason we don't allow arbitrary "unchecked" feature flags? This seems to cover many cases of new feature flags.
Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that Vaultwarden does not support CXP (credential exchange protocol) for import/export, and sent out #6853 for adding the client side feature flags.
During the investigation, I noticed that there are many Bitwarden feature flags that are not available on vaultwarden. Most of the feature flags seem to require nothing but pass a map entry of key:"true" in the api config.
I'm wondering, as a popular self-hosting solution, is there a reason we don't allow arbitrary "unchecked" feature flags? This seems to cover many cases of new feature flags.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions