Project

General

Profile

Actions
Copy link

Bug #2256

closed

J1.6: Password Autogenerate set to Yes - still requires backend user creation to set passwords

Bug #2256: J1.6: Password Autogenerate set to Yes - still requires backend user creation to set passwords

Added by nant almost 15 years ago. Updated almost 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
beat
Target version:
CB 1.4.0
Start date:
28 January 2011
Due date:
% Done:

100%

Estimated time:
1:00 h

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

2256.patch (1.2 KB) 2256.patch krileon, 01 February 2011 20:34

Updated by krileon almost 15 years ago Actions
Copy link
 #1

  • 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.

Updated by krileon almost 15 years ago Actions
Copy link
 #2

  • 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

Updated by beat almost 15 years ago Actions
Copy link
 #3

  • 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

Updated by krileon almost 15 years ago Actions
Copy link
 #4

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.

Updated by krileon almost 15 years ago Actions
Copy link
 #5

Confirmed is also the case in J15 (using the above steps to reproduce); is not J16 specific.

Updated by krileon almost 15 years ago Actions
Copy link
 #6

  • File 2256.patch 2256.patch added
  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100

Updated by beat almost 15 years ago Actions
Copy link
 #7

  • Status changed from Resolved to Closed
  • Estimated time set to 1:00 h

Fixed in commit r1408 in other way and tested by Kyle

Actions
Copy link

Also available in: PDF Atom