Item9226: internal server error when changing password of unkown user
Priority: Urgent
Current State: Closed
Released In: 1.1.0
Target Release: minor
Applies To: Engine
Component:
Branches:
- enable AllowLoginName in
configure
- go to ChangePassword
- LoginName = foo (use some unknown login name)
- passwords = bar
- hit submit
you get
Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information.
cannot change user passwords using Foswiki::BaseUserMapping
should be an oops unknown user
foo
.
Can somebody repro?
--
MichaelDaum - 29 Jun 2010
I tried to reproduce this on a vanilla trunk checkout. Followed the instructions above to the letter. I get a nice "Incorrect password" screen, which is correct because it doesn't give away the fact that there's no user called "foo".
I'm afraid it's down to you to zero in on this, unless someone else can reproduce it....
--
CrawfordCurrie - 29 Jun 2010
I get "Incorrect password" when
AllowLoginName
is
disabled
I get an internal error when enabling it.
Can anybody else please check?
--
MichaelDaum - 30 Jun 2010
I can confirm - With ASSERTs enabled, it fails because the cUID is undefined.
Assertion failed!
at /var/www/foswiki/trunk/core/lib/Assert.pm line 78
Assert::ASSERT(undef) called at /var/www/foswiki/trunk/core/lib/Foswiki/Users.pm line 1000
Foswiki::Users::setPassword('Foswiki::Users=HASH(0x848ec68)', undef, 'asdfasdf', 'qwerqwer') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI/Passwords.pm line 339
Foswiki::UI::Passwords::changePasswordAndOrEmail('Foswiki=HASH(0x848e838)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI/Manage.pm line 63
Foswiki::UI::Manage::_action_changePassword('Foswiki=HASH(0x848e838)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI/Manage.pm line 45
Foswiki::UI::Manage::manage('Foswiki=HASH(0x848e838)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI.pm line 310
Foswiki::UI::__ANON__() called at /usr/lib/perl5/vendor_perl/5.10.1/Error.pm line 415
eval {...} called at /usr/lib/perl5/vendor_perl/5.10.1/Error.pm line 407
Error::subs::try('CODE(0x804e2c8)', 'HASH(0x848e568)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI.pm line 429
Foswiki::UI::_execute('Foswiki::Request=HASH(0x844d000)', 'CODE(0x806fbc0)', 'manage', 1) called at /var/www/foswiki/trunk/core/lib/Foswiki/UI.pm line 277
Foswiki::UI::handleRequest('Foswiki::Request=HASH(0x844d000)') called at /var/www/foswiki/trunk/core/lib/Foswiki/Engine/CGI.pm line 30
Foswiki::Engine::CGI::run('Foswiki::Engine::CGI=HASH(0x81fa7f8)') called at manage line 24
at /var/www/foswiki/trunk/core/lib/Assert.pm line 78
Assert::ASSERT(undef) called at /var/www/foswiki/trunk/core/lib/Foswiki/Users.pm line 1000
Foswiki::Users::setPassword('Foswiki::Users=HASH(0x848ec68)', undef, 'asdfasdf', 'qwerqwer') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI/Passwords.pm line 339
Foswiki::UI::Passwords::changePasswordAndOrEmail('Foswiki=HASH(0x848e838)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI/Manage.pm line 63
Foswiki::UI::Manage::_action_changePassword('Foswiki=HASH(0x848e838)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI/Manage.pm line 45
Foswiki::UI::Manage::manage('Foswiki=HASH(0x848e838)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI.pm line 310
Foswiki::UI::__ANON__() called at /usr/lib/perl5/vendor_perl/5.10.1/Error.pm line 415
eval {...} called at /usr/lib/perl5/vendor_perl/5.10.1/Error.pm line 407
Error::subs::try('CODE(0x804e2c8)', 'HASH(0x848e568)') called at /var/www/foswiki/trunk/core/lib/Foswiki/UI.pm line 429
Foswiki::UI::_execute('Foswiki::Request=HASH(0x844d000)', 'CODE(0x806fbc0)', 'manage', 1) called at /var/www/foswiki/trunk/core/lib/Foswiki/UI.pm line 277
Foswiki::UI::handleRequest('Foswiki::Request=HASH(0x844d000)') called at /var/www/foswiki/trunk/core/lib/Foswiki/Engine/CGI.pm line 30
Foswiki::Engine::CGI::run('Foswiki::Engine::CGI=HASH(0x81fa7f8)') called at manage line 24.
--
GeorgeClark - 05 Jul 2010
Added a check to Password.pm - seems to be fixed.
--
GeorgeClark - 05 Jul 2010
Just a check.
Was this issue in 1.0.9? Is so please change status to Waiting For Release. If is was introduced in trunk after 1.0.9 was branched off then leave it closed.
Remember to set the target release field.
--
KennethLavrsen - 05 Jul 2010
.. was only on trunk.
--
MichaelDaum - 05 Jul 2010