From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Cristiano Panvel <cristiano(dot)panvel(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL and OpenLdap |
Date: | 2007-02-13 19:14:59 |
Message-ID: | 45D20E33.808@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Cristiano Panvel wrote:
> It does not appear nothing in log, only in /var/log/message the error
> of failed in login.
>
> Feb 13 12:04:16 fns4 postgres[7055]: [4-1] FATAL: LDAP authentication
> failed for user "scott"
> Feb 13 12:04:20 fns4 postgres[7056]: [4-1] FATAL: LDAP authentication
> failed for user "scott"
> Feb 13 12:04:20 fns4 postgres[7057]: [4-1] FATAL: LDAP authentication
> failed for user "scott"
> Feb 13 12:45:57 fns4 postgres[7216]: [4-1] FATAL: LDAP authentication
> failed for user "sflo"
> Feb 13 12:46:10 fns4 postgres[7223]: [4-1] FATAL: LDAP authentication
> failed for user "dbadm"
There definitely should be more than that. Note however that most of
these things are not classified as errors, so they are logged at LOG
level. It may be that you're filtering so you're not showing LOG level
information, or perhaps your syslogd is configured to write them to a
different file.
AFAICS, the only code-path that does not log *why* it rejected the
authentication is the case when the client refuses to send a password.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-02-13 19:23:58 | Re: Having a problem with my stored procedure |
Previous Message | Steve Wampler | 2007-02-13 19:04:55 | Re: Function in psql to Compare two numbers and return the bigger value |