?
avatar brianteeman
brianteeman
25 Aug 2016

Steps to reproduce the issue

In the admin go to the users options and the passwords tab. Set some options such as 5 symbols, 6 digits and 7 uppercase characters

Try to create a user in the admin or front end with a simple password such as 123456 and you can not because of the options that you set.

Now in the admin create a new user but do NOT create a password. This should create the user and email the username and password to the user

Expected result

Password generated in the email will conform to the settings in the user component options

Actual result

Random 9 character password

Votes

# of Users Experiencing Issue
1/1
Average Importance Score
3.00

avatar brianteeman brianteeman - open - 25 Aug 2016
avatar brianteeman brianteeman - change - 25 Aug 2016
The description was changed
avatar brianteeman brianteeman - edited - 25 Aug 2016
avatar brianteeman brianteeman - change - 25 Aug 2016
Category Authentication
avatar RonakParmar
RonakParmar - comment - 26 Aug 2016

I have follow above steps and able to reproduce this issue. Auto generated password is not as per my settings.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11798.

avatar zero-24 zero-24 - change - 26 Aug 2016
Status New Confirmed
avatar bhavikTailored
bhavikTailored - comment - 26 Aug 2016
  • I have follow above steps, auto generated password is not working as per admin settings.
  • screen shot 2016-08-26 at 02 17 41
  • screen shot 2016-08-26 at 02 18 55


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11798.

avatar zero-24
zero-24 - comment - 26 Aug 2016

Hmm maybe we should enable PW reset automagic if we generate a PW as well as generate a 32 char random passwort?

avatar brianteeman brianteeman - change - 26 Aug 2016
Labels Added: ?
avatar brianteeman
brianteeman - comment - 26 Aug 2016

@zero-24 no - we should just make sure that an autogenerated password follows the same rules as defined in the options as a user created password

avatar jeckodevelopment
jeckodevelopment - comment - 26 Aug 2016

yes, never noticed this before. But I agree with Brian.
If you setup a password policy in the backend, it must be respected if you choose to generate automatically password.

avatar mbabker
mbabker - comment - 26 Aug 2016

It's not so easy to do that because the random passwords are coming in by way of random_bytes() (and appropriate PHP 5 backports). It's somewhat hard to create random strings with certain guidelines when you don't have full control over the randomizing functions.

avatar jeckodevelopment
jeckodevelopment - comment - 26 Aug 2016

uhm... and what about disabling the automatic password generator when a different policy for password has been configured?

avatar zero-24
zero-24 - comment - 26 Aug 2016

it never uses the config. it is just a random string.

avatar mbabker
mbabker - comment - 26 Aug 2016

Long and short, if you've got a password policy enabled, unless you grab a massively large block of data from random_bytes() and keep appending characters to the string until you match policy, it's not viable to use random_bytes() as a password generator that has to be policy aware.

Which means changing how the user record is handled in that case. Do you allow NULL passwords or do you cause form validation errors (which prevents saving) on an empty value?

avatar brianteeman
brianteeman - comment - 9 Dec 2016

So long and farewell

avatar brianteeman brianteeman - change - 9 Dec 2016
The description was changed
Status Confirmed Closed
Closed_Date 0000-00-00 00:00:00 2016-12-09 15:34:59
Closed_By brianteeman
avatar brianteeman brianteeman - close - 9 Dec 2016

Add a Comment

Login with GitHub to post a comment