github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-08-27 05:35:03 -05:00
Code Issues 534 Packages Projects Releases 86 Wiki Activity

Organization settings #4308

New Issue
Closed
opened 2026-03-07 19:39:26 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-03-07 19:39:26 -06:00
Owner
Copy Link
Copy Source

Originally created by @bokkabonga on GitHub (Apr 2, 2020).

Subject of the issue

Organizations seem to have some settings about 2FA, the master password and the password generator that can be changed by the owner. In german they are called "Richtlinien" so i guess the English term would be "Policies".
Changing those "Policies" doesn´t change anything. I am not sure if this has been implented yet, but i couldn´t find any other Issue concerning this.

Your environment

  • Bitwarden_rs version: 1.14.1-843604c9
  • Install method: built from source
  • Clients used: Web-Vault
  • Reverse proxy and version: none
  • Version of mysql/postgresql: mariadb 10.4

Steps to reproduce

Changed the Policy for the password generator to at least 24 Signs and to include upper and lower, numbers and special characters. I made sure that the "Activate" checkbox was ticked and hit "Save".

Expected behaviour

When generating a new password for an entry in the organization, the password should be generated according to the rules set.

Actual behaviour

The password is generated with the default pattern (14 charakters, both upper and lower and numbers).

Relevant logs

Originally created by @bokkabonga on GitHub (Apr 2, 2020). <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unneccessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS adresses and especially passwords, if neccessary. --> ### Subject of the issue Organizations seem to have some settings about 2FA, the master password and the password generator that can be changed by the owner. In german they are called "Richtlinien" so i guess the English term would be "Policies". Changing those "Policies" doesn´t change anything. I am not sure if this has been implented yet, but i couldn´t find any other Issue concerning this. ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: 1.14.1-843604c9 <!-- How the server was installed: Docker image / package / built from source --> * Install method: built from source * Clients used: Web-Vault * Reverse proxy and version: none * Version of mysql/postgresql: mariadb 10.4 ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start bitwarden_rs? --> Changed the Policy for the password generator to at least 24 Signs and to include upper and lower, numbers and special characters. I made sure that the "Activate" checkbox was ticked and hit "Save". ### Expected behaviour <!-- Tell us what should happen --> When generating a new password for an entry in the organization, the password should be generated according to the rules set. ### Actual behaviour <!-- Tell us what happens instead --> The password is generated with the default pattern (14 charakters, both upper and lower and numbers). ### Relevant logs <!-- Share some logfiles, screenshots or output of relevant programs with us. -->
GiteaMirror commented 2026-03-07 19:39:27 -06:00
Author
Owner
Copy Link
Copy Source

@BlackDex commented on GitHub (Apr 2, 2020):

Hello @bokkabonga,

It seems you have to logout and back in again for this to work.
I tested this on the upstream bitwarden project, and it acts the same.
It probably needs a sync/refresh of these items.

Maybe you can report a bug to the upstream project and log past it's link here so we can track it if needed.

@BlackDex commented on GitHub (Apr 2, 2020): Hello @bokkabonga, It seems you have to logout and back in again for this to work. I tested this on the upstream bitwarden project, and it acts the same. It probably needs a sync/refresh of these items. Maybe you can report a bug to the upstream project and log past it's link here so we can track it if needed.
GiteaMirror commented 2026-03-07 19:39:28 -06:00
Author
Owner
Copy Link
Copy Source

@bokkabonga commented on GitHub (Apr 2, 2020):

Hey @BlackDex,

Logging out and back in did indeed do the trick for me. Thanks a lot! I will try to open a bug report in the upstream project next week at latest and leave the link here so it can be tracked.

Thanks a lot for your help :)

@bokkabonga commented on GitHub (Apr 2, 2020): Hey @BlackDex, Logging out and back in did indeed do the trick for me. Thanks a lot! I will try to open a bug report in the upstream project next week at latest and leave the link here so it can be tracked. Thanks a lot for your help :)
GiteaMirror commented 2026-03-07 19:39:28 -06:00
Author
Owner
Copy Link
Copy Source

@giss69 commented on GitHub (May 10, 2020):

i have the same issue on Version: 1.14.2-8bbbff75. i can not change master password because of the password regulation. Logging out and back didn't help.

@giss69 commented on GitHub (May 10, 2020): i have the same issue on Version: 1.14.2-8bbbff75. i can not change master password because of the password regulation. Logging out and back didn't help.
GiteaMirror commented 2026-03-07 19:39:28 -06:00
Author
Owner
Copy Link
Copy Source

@dani-garcia commented on GitHub (May 13, 2020):

What do you mean you can't change the password because of the policy? As long as you follow the policies it should allow you to change it just fine.

@dani-garcia commented on GitHub (May 13, 2020): What do you mean you can't change the password because of the policy? As long as you follow the policies it should allow you to change it just fine.
GiteaMirror commented 2026-03-07 19:39:28 -06:00
Author
Owner
Copy Link
Copy Source

@giss69 commented on GitHub (May 14, 2020):

@dani-garcia
i get always thins error:
your new master password does not meet the policy requirements
but it does.

@giss69 commented on GitHub (May 14, 2020): @dani-garcia i get always thins error: `your new master password does not meet the policy requirements` but it does.
GiteaMirror commented 2026-03-07 19:39:29 -06:00
Author
Owner
Copy Link
Copy Source

@BlackDex commented on GitHub (Oct 9, 2020):

@giss69 are you still having this issue? If so, could you give use a real life example of the settings for the policy what had been configured and what kind of password isn't allowed?

@BlackDex commented on GitHub (Oct 9, 2020): @giss69 are you still having this issue? If so, could you give use a real life example of the settings for the policy what had been configured and what kind of password isn't allowed?
GiteaMirror commented 2026-03-07 19:39:29 -06:00
Author
Owner
Copy Link
Copy Source

@BlackDex commented on GitHub (Nov 18, 2020):

Closing this ticket because of inactivity.
Feel free to re-open if the issue isn't resolved using the testing/master version.

@BlackDex commented on GitHub (Nov 18, 2020): Closing this ticket because of inactivity. Feel free to re-open if the issue isn't resolved using the `testing`/`master` version.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#4308