# Different password policies for different groups?

**URL:** <https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747>\
**Category:** ℹ️ Support\
**Created:** [November 7, 2023, 10:44am UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747 "2023-11-07T10:44:49Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giuseppe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/giuseppe/32/21391_2.png) [@Giuseppe](https://help.nextcloud.com/u/Giuseppe)\
**Post date:** [November 7, 2023, 10:44am UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/1 "2023-11-07T10:44:49Z")

</div>

I want to have different password policies for different kind of users, like

- 10 char, whatever, if user has TOTP enabled
- 25 char, obnoxious requirements, otherwise.

Is this a feature of any app I can install?

---

<div class="post-metadata">

**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/6_22734026db12803ebb3e059622ac3534.png) [@bb77](https://help.nextcloud.com/u/bb77)\
**Post date:** [November 7, 2023, 12:25pm UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/2 "2023-11-07T12:25:05Z")

</div>

As far as I know, this is not possible, and I am not aware of any app that offers such a feature.

My recommendation would be to choose a good middle ground for the password lenght, e.g. 16 characters for all users, enforce strong passwords and limit the Number of login attempts. Example:

 ![Bildschirmfoto vom 2023-11-07 13-18-16](https://help.nextcloud.com/uploads/default/original/3X/4/e/4ea16865e9636f37a20c7bd0f7b7507618e461d3.png)

Or even better, just enforce 2FA for all users, and perhaps offer other 2FA methods such as WebAuthn as well, for users that prefer to use a security key instead of TOTP.

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [November 7, 2023, 1:38pm UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/3 "2023-11-07T13:38:43Z")

</div>

@Giuseppe  
You can not compare passwords (strong or weak) with 2FA that makes no sense. Also strong passwords can be read by keylogger and then strong passwords help nothing. Use 2FA or don’t use it. But don’t try to fake security with passwords that doesn’t exist. You won’t achieve anything with a password length of 25 characters instead of 10, as this is completely irrelevant for all attack scenarios apart from decrypting password databases.

---

<div class="post-metadata">

**Author:** ![Giuseppe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/giuseppe/32/21391_2.png) [@Giuseppe](https://help.nextcloud.com/u/Giuseppe)\
**Post date:** [November 7, 2023, 2:26pm UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/4 "2023-11-07T14:26:01Z")

</div>

I know.

I have some users that I cannot enforce 2FA on (they’re shared accounts). For everybody else, I’d be happy enough with a bad password plus enforced OTP.

But without OTP, your password actually has to be good, and it won’t be if I don’t enforce it.

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [November 7, 2023, 2:29pm UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/5 "2023-11-07T14:29:24Z")

</div>

@Giuseppe  
The problem is rather that the users share the account. You should solve this by creating your own accounts. Shared accounts do not meet any security or compliance requirements.

If the users only use a Nextcloud client, you could perhaps use app passwords. Then you neither have the password problem nor do the users need 2FA.

---

<div class="post-metadata">

**Author:** ![Giuseppe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/giuseppe/32/21391_2.png) [@Giuseppe](https://help.nextcloud.com/u/Giuseppe)\
**Post date:** [November 7, 2023, 2:30pm UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/6 "2023-11-07T14:30:46Z")

</div>

I know that too, but our workflow runs on this assumption. We’ll eventually move everybody on individual accounts.

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [November 7, 2023, 2:34pm UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/7 "2023-11-07T14:34:12Z")

</div>

Then you probably only have 25 characters for all users. In my case, I would probably generate an MD5 fingerprint based on an easy-to-remember character string that changes every month and then capitalize the first letter, for example, and add one special character at the end in accordance with the requirements for your password rules. Then the length is 33 characters and all is ok and i can easy recreate it. I hate password manager. How long is the password of your password manager? 25 characters or 10 characters? Without 2FA i think 25 characters is better. 😉

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 14, 2024, 1:16pm UTC](https://help.nextcloud.com/t/different-password-policies-for-different-groups/173747/8 "2024-12-14T13:16:27Z")

</div>


