[SOLVED] Create user => error password must not be empty!

[Evelin]

Hi, I tried to create a user but I cannot save it because of a missing password. I think this happens because of a missing or wrong confuguration but I'm not sure. Can you advice?

This is what I did in TestLink 1.9.10:
1. Logon with administrator permissions
2. Go to User Management > View Users
3. Scroll down and click Create > the User details screen opens
4. Check the fields in User details: Login, First Name, Last Name, Email, Role, Locale, Authentication method, Active. No Password field. Authentication method in our case: Default() (other options: DB, LDAP)
5. Fill in all fields, change authentication method to DB
6. Check fields again - still no password field
7. Click save

Recent behaviour: Error message: The password must not be empty! We also tried authentication methods Default() and LDAP, with the same result: The fields on the screen stay the same, and at Save the error 'The password must not be empty!' is displayed.
What I expected: Password field(s) are shown when creating a user with DB authentication.

What I have checked already:
Mantis for user management issues (nothing found that refers to the error message above)
Installation and Configuration + TestLink 1.9 forum (nothing found that refers to the error message above or configuring authentication method in config.inc)
TestLink > EventViewer does not list any events regarding user management and authentication.
custom_config.inc.php > No changes were made regarding user management and authentication.
Configuration /* Default Authentication method */ in config.inc.php > $tlCfg->authentication['method'] = 'MD5';

Do we have to replace MD5 by DB?

Thanks for your attention

[narsu]

Hello I found same issue with my installation. Glad I found this thread!

http://forum.testlink.org/viewtopic.php ... ord#p18767

Let's focus further discussion here?


br,
Narsu

[narsu]

More info

I noticed I was using old version of custom_config_inc.php which had default value for authentication. I forgot to edit it first

I just changed MD5 -> DB in original config file but I forgot to edit custom_config_inc.php which should be primary target for tuning.

br,
Narsu

[narsu]

Ok! it's working now!

You have to replace MD5 value with DB ! Remember to update custom_config_inc.php file if you are using it !
Look at solution http://forum.testlink.org/viewtopic.php ... 771#p18771

br,
Narsu

[fman]

1. get lastest code from gitorious
2. fresh install
3. create first test project
4. access create user feature, auth combo box is presetted to Default(DB). Set to DB,
Password filed is PRESENT.
5. user created without issue.

I'm going to try with an DB from 1.9.9 and see what is happening, may be issue can be related to value on users table , field => "auth_method" VARCHAR(10) NULL DEFAULT '',

Please open issue with ALL DETAILS AND NOT ONLY WITH REFERENCE TO THIS POST, on mantis

[fman]

I think Evelyn has the ANSWER => set DB instead of MD5.
I'm sorry for the inconvenience, and the missing details of config change.
Please do changes and provide feedback.

If you still has MD5 on your config.inc.php instead of DB, this means THAT YOU DO NOT HAVE 1.9.10, but a mixed up version, and this is not GOOD

[fman]

ATTENTION ALSO TO THIS:
If your DEFAULT AUTH METHOD is DB, and when creating a user you choose LDAP, I've done NO Javascript TRICK to remove PASSWORD field, it will remain there but will be useless, but you need to fill it (lazy approach)

[Evelin]

With DB instead of MD5 we cannot login anymore. This will probably be some configuration issue but right now we cannot do more testing because we cannot interrupt the users. We will set up a test system on Monday June 6, then test again and come back with a qualified feedback or error report if necessary.

>> OK, solved. We tested again on a test system and everything was well. Productive TestLink is ok, too. I think that we tried the user management in a stage when the installation was not a clean 1.9.10, then switched to MD5 because we needed to create a user. Then, we repaired the installation and switched back to DB, and it's ok now.