300390 - cannot add new users on 2.20rc1 from editusers.cgi

Status: RESOLVED FIXED

(Bugzilla :: User Accounts, defect)

Description

[Ignacio Galmarino]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050524 Firefox/1.0 (Ubuntu package 1.0.2 MFSA2005-44)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050524 Firefox/1.0 (Ubuntu package 1.0.2 MFSA2005-44)

When a new user login (not in the database yet) i get this message:

Undefined subroutine &Bugzilla::User::bz_crypt called at Bugzilla/User.pm line
1141, <DATA> line 283.

This does not happend if the user is already in the database (has already logon
once before).

I change this line in User.pm

sub insert_new_user ($$;$$) {
    my ($username, $realname, $password, $disabledtext) = (@_);
    my $dbh = Bugzilla->dbh;

    $disabledtext ||= '';

    # If not specified, generate a new random password for the user.
    $password ||= &::GenerateRandomPassword();
    #my $cryptpassword = bz_crypt($password);  <===== OLD
    my $cryptpassword = "password";            <===== NEW

And everything works ok.

Be really carefull because i dont know if this is ok ...

Ignacio


Reproducible: Always

Steps to Reproduce:
1. Configure LDAP Auth
2. Login with a new user (never logon before)


Actual Results:  
Get the error message

Comment 1

[Frédéric Buclin]

No need to use LDAP. Happens in all cases when a new user is added, in my
testcase from editusers.cgi:

Undefined subroutine &Bugzilla::User::bz_crypt called at Bugzilla/User.pm line 1140.

Comment 2

[Max Kanat-Alexander]

I can't reproduce this on landfill.
http://landfill.bugzilla.org/bugzilla-2.20-branch/ or
http://landfill.bugzilla.org/bugzilla-tip/

I can create accounts quite easily.

Comment 3

[Max Kanat-Alexander]

Ahhh, I see. The *admin* can't make users. createaccount.cgi works fine.

Comment 4

[Frédéric Buclin]

Fixed by blocker

Comment 5

[Frédéric Buclin]

*** Bug 300859 has been marked as a duplicate of this bug. ***

Comment 6

[Frédéric Buclin]

*** Bug 301623 has been marked as a duplicate of this bug. ***

Comment 7

[jessn]

I have recently seen this bug in version 2.20rc1.

Comment 8

[Max Kanat-Alexander]

Yes, it will be fixed in 2.20rc2.