Re: ident changes between 8.3 and 8.4 - Mailing list pgsql-hackers

From Rafael Martinez
Subject Re: ident changes between 8.3 and 8.4
Date
Msg-id 4AF2EA8A.80703@usit.uio.no
Whole thread Raw
In response to Re: ident changes between 8.3 and 8.4  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew Dunstan wrote:
> 
>
>>> Is this a bug or have we decided this behavior? I can not find any
>>> documentation explaining that 'sameuser' is not a valid mapname.
>>>     
>> To make 8.4 behave like the previous "ident sameuser" way, just put
>> "ident". No map is needed.
>>   
> And it is documented in the release notes:
> <http://www.postgresql.org/docs/current/static/release-8-4.html>, which
> the OP should have read when upgrading.
> 
>

Hei

The release note was read some time ago and it was most probably
misinterpreted.

The release note says:
"Change all authentication options to use name=value syntax"
"Remove the ident sameuser option, instead making that behavior the
default if no usermap is specified"

It says that 'ident sameuser' have been removed, but it does not say
anything about "ident map=sameuser" not being a valid way of defining a
mapname = sameuser.

I still cannot find any references to this under:
19.2. Username maps
19.3.6. Ident-based authentication

Anyway, we know the reason of this behavior now, so this is not a
problem for us anymore, although it could be confusing for others.

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)

iD8DBQFK8uqIBhuKQurGihQRAhZjAKCVJpZ5x0oXXQ2+cfp5TJizl5jj1ACfaTb0
agXmanpgeo94RWP33drqNJY=
=2OkL
-----END PGP SIGNATURE-----


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: operator exclusion constraints
Next
From: Tommy Gildseth
Date:
Subject: Re: ident changes between 8.3 and 8.4