-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello
We have been using for years and without problems local ident
autentification in the database for our user postgres.
These are the values that we have been using until version 8.3:
pg_hba.conf:
- ------------
local all postgres ident sameuser
pg_ident.conf:
- --------------
sameuser postgres postgres
With 8.4, we get this error if we use a map named 'sameuser'.
- -----------------------------------------------------------
FATAL: Ident authentication failed for user "postgres"
LOG: no match in usermap for user "postgres" authenticated as "postgres"
CONTEXT: usermap "sameuser"
- -----------------------------------------------------------
These are the values used with 8.4:
pg_hba.conf:
- ------------
local all postgres ident map=sameuser
pg_ident.conf:
- --------------
sameuser postgres postgres
After some investigation, we have found out that everything works
without problems if we change the mapname used by ident to something
different than 'sameuser'.
Is this a bug or have we decided this behavior? I can not find any
documentation explaining that 'sameuser' is not a valid mapname.
regards,
- --Rafael Martinez, <r.m.guerrero@usit.uio.no>Center for Information Technology ServicesUniversity of Oslo, Norway
PGP Public Key: http://folk.uio.no/rafael/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
iD8DBQFK8tesBhuKQurGihQRAlYJAKCj079582JocEUoIZfCLbqmsFeo0gCeMdYs
AifiS+Giu8M0r8SJLUYoEyM=
=e+Vz
-----END PGP SIGNATURE-----
