starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #944] Organization settings #667

New issue
Closed
opened 2026-03-03 02:01:58 +03:00 by kerem · 7 comments
kerem commented 2026-03-03 02:01:58 +03:00
Owner
Copy link

Originally created by @bokkabonga on GitHub (Apr 2, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/944

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). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/944 <!-- 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. -->
kerem closed this issue 2026-03-03 02:01:59 +03:00
kerem commented 2026-03-03 02:02:00 +03:00
Author
Owner
Copy link

@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.

<!-- gh-comment-id:607842509 --> @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.
kerem commented 2026-03-03 02:02:00 +03:00
Author
Owner
Copy link

@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 :)

<!-- gh-comment-id:607851711 --> @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 :)
kerem commented 2026-03-03 02:02:00 +03:00
Author
Owner
Copy link

@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.

<!-- gh-comment-id:626296551 --> @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.
kerem commented 2026-03-03 02:02:00 +03:00
Author
Owner
Copy link

@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.

<!-- gh-comment-id:628265914 --> @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.
kerem commented 2026-03-03 02:02:00 +03:00
Author
Owner
Copy link

@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.

<!-- gh-comment-id:628408694 --> @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.
kerem commented 2026-03-03 02:02:00 +03:00
Author
Owner
Copy link

@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?

<!-- gh-comment-id:706417293 --> @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?
kerem commented 2026-03-03 02:02:00 +03:00
Author
Owner
Copy link

@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.

<!-- gh-comment-id:729653129 --> @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
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.8
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
1.35.2
1.35.1
1.35.0
1.34.3
1.34.2
1.34.1
1.34.0
1.33.2
1.33.1
1.33.0
1.32.7
1.32.6
1.32.5
1.32.4
1.32.3
1.32.2
1.32.1
1.32.0
1.31.0
1.30.5
1.30.4
1.30.3
1.30.2
1.30.1
1.30.0
1.29.2
1.29.1
1.29.0
1.28.1
1.28.0
1.27.0
1.26.0
1.25.2
1.25.1
1.25.0
1.24.0
1.23.1
1.23.0
1.22.2
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.0
1.17.0
1.16.3
1.16.2
1.16.1
1.16.0
1.15.1
1.15.0
1.14.2
1.14.1
1.14
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
Labels
Clear labels   
SSO

   
Third party

   
better for forum

   
bug

   
bug

   
documentation

   
duplicate

   
enhancement

   
future Vault

   
future Vault

   
future Vault

   
good first issue

   
help wanted

   
low priority

   
notes

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
troubleshooting

   
wontfix
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#667
No description provided.