[horde] v4.0.9 - Account locking and tracking question

Ralf Lang lang at b1-systems.de
Fri Sep 16 19:19:54 UTC 2011


Am Freitag, 16. September 2011, 21:02:20 schrieb Torsten Krah:
> Am Freitag, den 16.09.2011, 20:57 +0200 schrieb Ralf Lang:
> > No, the feature is driver independent. It only depends on history and
> > locks,
> > both usually configured to use the default sql backend.
> 
> Locks are configured to use the Postgresql backend - history i don't
> know where to configure, but a table called horde_histories is there.
> 
> > Can you check if false logins create any entries in the history
> > tables?
> 
> Looked at following tables:
> 
> horde_locks - is empty, before and after the false login, rows = 0.
> horde_histories - before failed login 1831 rows, after 1831 rows - so
> nothing new there.
> 
> Any other table i should look at?

Currently no idea. 
Can you post the complete 
[auth]
[lock]
and [history]

sections of your conf.php?
I'll try to reproduce.

-- 
Ralf Lang
Linux Consultant / Developer

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


More information about the horde mailing list