[Tickets #12081] Re: badlogin not working whith IMP authentication

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12081
------------------------------------------------------------------------------
  Ticket             | 12081
  Updated By         | patrick.vangilst at labri.fr
  Summary            | badlogin not working whith IMP authentication
  Queue              | Horde Groupware Webmail Edition
  Version            | 5.0.4
  Type               | Bug
  State              | Not A Bug
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


patrick.vangilst at labri.fr (2013-03-05 10:39) wrote:

Ok, the BADLOGIN Exception is actually thrown (in /imp/lib/Imap/Exception.php)

I think I found my problem:
In /usr/share/pear/Horde/Auth/Base.php, there is a test before calling  
$this->_badLogin($userId);
Here is the test:

  if (($code == Horde_Auth::REASON_BADLOGIN) &&
                     $this->hasCapability('badlogincount')) {
                     $this->_badLogin($userId);
                 }

If I comment the line  $this->hasCapability('badlogincount')), bad  
logins are stored in the database (horde_histories) which seems ok...

Now, I can see in the same file, the constructor with another test:

if (isset($params['history_api'])) {
             $this->_history_api = $params['history_api'];
             $this->_capabilities['badlogincount'] = true;
             unset($params['history_api']);
         }

Maybe, the problem is here, so the question is:
How can I enable $params['history_api'] ???
Tell me if I am wrong or, if I'm right, how do I enable this param???
Thanks in advance.