User does not get informed about sharing password violating policy

[andrewgs67]

Hi!
When user shares folder or file via link, he must set password for link.
If password mismatch complexity requirements share link not created and user not notified about password mismatch, not showing any errors messages, notifications about password policy mismatching. Instead, if password too short, splash notification windows displayed for user.
And I can’t find exactly requirements for passwords complexity - for example, why password “Qwerty4321” mismatch, but password “WSXedc321” allowed.
NextCloud 16.0.1.1, CentOS 7, nginx , PHP 7.3.4, php-fpm, MariaDB 10.4.4
In browser all acivities for Nextcloud host allowed.
Thanks,
Best regards,
Andrew.

[wiswedel]

CC @nextcloud/designers

[juliusknorr]

@skjnldsv Maybe something for https://github.com/orgs/nextcloud/projects/32 ?

[skjnldsv]

Definitely!

[andrewgs67]

Hi! Sorry, I did not find any likes for my feuature request. вт, 18 июн. 2019 г. в 22:53, Julius Härtl <notifications@github.com>:

…

@skjnldsv <https://github.com/skjnldsv> Maybe something for https://github.com/orgs/nextcloud/projects/32 ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#15983?email_source=notifications&email_token=AJMLV22OYMMUFRHUT7ENSTTP3E4LZA5CNFSM4HYWA3SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7YTJQ#issuecomment-503286182>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJMLV25IVWRR3J4SE7AKIITP3E4LZANCNFSM4HYWA3SA> .

-- Best Regards, Andrew

[wiswedel]

Related: #12171

[jancborchardt]

Yes, all this password policy and giving feedback to people is just a huge mess. No one wants to get their head around password policies, so a proper solution here is what @wiswedel already linked:
Password protection for link shares should suggest autogenerated passwords #12171

I would tend to close this one in favor of that. @andrewgs67 do you agree that it would solve your issue?

[jancborchardt]

(Btw @wiswedel "good first issue" are only small bugs where there is enough documentation on where what needs to be changed so that a newcomer to the project could immediately fix it. This issue seems too big, has no defined solution and it isn’t clear in which file one should start looking to fix it. 🙂 – But thanks for using the tag, and please do continue while keeping those criteria in mind.)