Bug #2256
closed
J1.6: Password Autogenerate set to Yes - still requires backend user creation to set passwords
Added by nant almost 14 years ago.
Updated almost 14 years ago.
Start date:
28 January 2011
Description
Just tested with CB 1.4 (internal build) and verified that the CB User Manager when creating backend users requires the password to be specified.
I think that it should not be the case.
Files
- Status changed from New to Feedback
- Assignee set to beat
- Target version set to CB 1.4.0
Works without backend validation, but believe it should not validate the password unless specified when auto-generate is enabled.
- Subject changed from Password Autogenerate set to Yes - still requires backend user creation to set passwords to J16: Password Autogenerate set to Yes - still requires backend user creation to set passwords
- Subject changed from J16: Password Autogenerate set to Yes - still requires backend user creation to set passwords to J1.6: Password Autogenerate set to Yes - still requires backend user creation to set passwords
To reproduce
Autogenerate random registration passwor: Yes
Fields validation in Admin: Yes
Attempt to create a user, but do NOT input a password. Try to save the user after inputting other mandatory data and page will refresh with the below JS pop-up.
"Password : This field is required!"
With Fields validation in Admin set to No, this issue does not happen. More or less it's validating the field regardless of autogenerate. Normally this would be ok, but with autogenerate it shouldn't care whether the password field is blank or not.
Confirmed is also the case in J15 (using the above steps to reproduce); is not J16 specific.
- File 2256.patch 2256.patch added
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
- Estimated time set to 1:00 h
Fixed in commit r1408 in other way and tested by Kyle
Also available in: Atom
PDF
Updated by 
Updated by