Re: step 2..

From: Oliver Fromme <olli(at)lurza(dot)secnetix(dot)de>
To: tallison(at)tacocat(dot)net (Tom Allison)
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: step 2..
Date: 2004-03-17 11:42:14
Message-ID: 200403171142.i2HBgEqH010827@lurza.secnetix.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice


Tom Allison wrote:
> psql: FATAL: IDENT authentication failed for user "foo"
>
> pg_hba.conf?
>
> I have entries like:
>
> local all postgres ident sameuser
> local all all ident sameuser
> host all all 127.0.0.1 255.255.255.255 ident sameuser
> host all all 0.0.0.0 0.0.0.0 reject

Mine looks like this:

#TYPE DBASE USER IP-ADDRESS IP-MASK METHOD
#---- ----- ---- ---------- ------- ------
local all all trust
host all all 127.0.0.1 255.255.255.255 trust
host fishdb simon 192.168.130.0 255.255.255.0 md5
host treedb janet 192.168.130.0 255.255.255.0 md5
host tigerdb marion 192.168.130.0 255.255.255.0 md5
... etc.

> I have the exact same user and password set in my login user files as
> what I created using the sql script above.

What do you mean by "login user files"? Database user are
not the same as login users. In fact, they _should_ not be
the same.

> I'm still getting the IDENT error.
> suggestions?

Not using "ident" authentication? It's insecure anyway.

Regards
Oliver

--
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"Python tricks" is a tough one, cuz the language is so clean. E.g.,
C makes an art of confusing pointers with arrays and strings, which
leads to lotsa neat pointer tricks; APL mistakes everything for an
array, leading to neat one-liners; and Perl confuses everything
period, making each line a joyous adventure <wink>.
-- Tim Peters

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Allison 2004-03-17 12:14:11 books
Previous Message Christian Pöcher 2004-03-17 10:13:58 Re: Removing "lost" locks