[Tickets #10228] Re: resetCredentials does not work after I change my password

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10228
------------------------------------------------------------------------------
  Ticket             | 10228
  Updated By         | kareem.dana at gmail.com
  Summary            | resetCredentials does not work after I change my
                     | password
  Queue              | Passwd
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


kareem.dana at gmail.com (2011-06-11 17:34) wrote:

I made the code changes that Ralf suggested and confirmed with  
getAuthCredential() that imp now has the new password in its  
$credential array but it still does not work.

It looks like IMP is still trying to access the IMAP server with the  
original IMAP object it created when I logged in initially and isn't  
attempting to login again. I added some debugging messages to the code  
to see what was going on:

Jun 11 12:13:18 test1 HORDE: HORDE [passwd] passwd: resetCredentials  
[pid 1466 on line 109 of  
"/usr/local/www/apache22/horde/passwd/lib/Passwd.php"]
Jun 11 12:13:18 test1 HORDE: HORDE [passwd] __call method alerts,  
params Array  [pid 1466 on line 329 of  
"/usr/local/www/apache22/horde/imp/lib/Imap.php"]
Jun 11 12:13:18 test1 HORDE: HORDE [imp] __call method status, params  
Array  [pid 1466 on line 329 of  
"/usr/local/www/apache22/horde/imp/lib/Imap.php"]
Jun 11 12:13:33 test1 HORDE: HORDE [imp] IMAP server denied  
authentication. [pid 1466 on line 343 of  
"/usr/local/www/apache22/horde/imp/lib/Imap.php"]

After resetCredentials is called, IMP never tries to login or do an  
imap open again. I think its still using the original ImapObject.  
createImapObject() is never called after the first login. Could this  
be an IMP bug?