Hi mbeaucha, thanks for the feedback. The fix was implemented such that it works along with password regex as explained in the crowd documentation page https://confluence.atlassian.com/display/CROWD/Configuring+an+Internal+Directory for Crowd Internal Directory. We can raise a new issue and discuss/investigate how to go about fixing this issue with OpenLDAP / AD.

I just upgraded to 2.5.2 to get this feature. It is very nicely implemented for the Crowd internal directory. Thanks! But unless I've missed it, it looks like there is no similar option for describing the requirements for an external (ex. OpenLDAP, AD, etc.) directory. Am I missing something or was this overlooked?

Issue fixed and merged into 2_5_stable.

One more thing that should be stated explicitly: the complexity requirements should be displayed to the user PRIOR to the user failing the requirements. As I mentioned in a previous comment, some users have a very hard time meeting complex requirements and they would be well served by being told the requirements ahead of composing their password to minimize their frustration.

I understand that it's more difficult to figure out which directory their so that you display the correct requirements. In our organization, the complexity requirements are set organization-wide, and do not differ between directories. I can't speak for how its done elsewhere.

Still crossing my fingers that this issue gets assigned to someone soon.

Also I just looked through CWD-1189 again. The "improved" complexity message displayed to users (which comes at a very bad time - even when things are going smoothly, password changes can be frustrating for some users) was added around 11/May/09 as part of CWD-1189. This issue had 13 votes and was not really addressed to anyone's satisfaction, but was closed.

This issue is actually much older than 14/May/12 and really seems to have been lost in the bug shuffle. Can it get some love?

This is vital for users of the self-service console when complexity requirements are set. At a sufficient level of complexity it is very difficult for a non-technical user to compose an appropriate password without some guidance regarding the requirements.

See Atlassian Answers for more use cases:

https://answers.atlassian.com/questions/17336/some-translates-for-crowd-errors?page=1#67587