X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0057C3A650A for ; Sun, 12 Dec 2004 03:56:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30761-03 for ; Sun, 12 Dec 2004 03:55:54 +0000 (GMT) Received: from pagoda.mtholyoke.edu (pagoda.mtholyoke.edu [138.110.30.68]) by svr1.postgresql.org (Postfix) with ESMTP id A46403A655B for ; Sun, 12 Dec 2004 03:55:56 +0000 (GMT) Received: from pagoda.mtholyoke.edu (rpeterso@pagoda [127.0.0.1]) by pagoda.mtholyoke.edu (8.12.11/8.12.11/Debian-5) with ESMTP id iBC3ttZi017214 for ; Sat, 11 Dec 2004 22:55:55 -0500 Received: (from rpeterso@localhost) by pagoda.mtholyoke.edu (8.12.11/8.12.11/Debian-5) id iBC3ttw0017211 for pgsql-admin@postgresql.org; Sat, 11 Dec 2004 22:55:55 -0500 From: Ron Peterson Date: Sat, 11 Dec 2004 22:55:55 -0500 To: pgsql-admin@postgresql.org Subject: Re: fallback authentication Message-ID: <20041212035555.GA17165@mtholyoke.edu> References: <20041210202050.GA12507@mtholyoke.edu> <20041211015056.GA13388@mtholyoke.edu> <20041211195107.GD2668@wolff.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041211195107.GD2668@wolff.to> Organization: Mount Holyoke College X-Operating-System: Debian GNU/Linux User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200412/103 X-Sequence-Number: 15689 On Sat, Dec 11, 2004 at 01:51:07PM -0600, Bruno Wolff III wrote: > On Fri, Dec 10, 2004 at 20:50:56 -0500, > Ron Peterson wrote: > > On Fri, Dec 10, 2004 at 03:20:50PM -0500, Ron Peterson wrote: > > > > > Sometimes, however, I would like to create an account in PostgreSQL > > > which I do not want to also maintain in LDAP. Is it possible to > > > configure authentication to fall through to a different method? > > > > I suppose the right thing to do is either > > > > * don't be lazy, and update my LDAP maintainance to include the > > required accounts, or > > > > * fall through in pam. Is there anything similar in concept to > > libpam-pgsql, but which simply authenticates against PostgreSQL's > > built-in authentication mechanism? > > You can put per user exceptions first in your pg_hba.conf file. That way > these people will be handled by those rules, but other users can be > authenticated using pam. I have: host all all 127.0.0.1 255.255.255.255 md5 host all all 127.0.0.1 255.255.255.255 pam postgresql host all all 0.0.0.0 0.0.0.0 reject I've also tried reversing the first two lines. Either strategy individually works, but I'd like lookups which don't work locally to try pam (or vice-versa). What am I missing? I have to use pam to authenticate my local userbase, unless I start also maintaining the necessary postgresql password hash. But I'd like to also have a few local administrative accounts that don't exist in ldap. Bottom line is, I can always put them in ldap if I really have to; I was just hoping there was a lazier way. I feel like I'm working harder at being lazy than if I'd just tweak my ldap account maintainance procedures, though... ;) -- Ron Peterson Network & Systems Manager Mount Holyoke College http://www.mtholyoke.edu/~rpeterso