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 16DC83A18B3 for ; Sun, 16 Jan 2005 09:10:37 +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 13750-10 for ; Sun, 16 Jan 2005 09:10:31 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by svr1.postgresql.org (Postfix) with ESMTP id 3CDAE3A18AD for ; Sun, 16 Jan 2005 09:10:32 +0000 (GMT) Received: from rasputin by 9.hellooperator.net with local (Exim 4.43) id 1Cq6QY-00028N-O4 for pgsql-admin@postgresql.org; Sun, 16 Jan 2005 09:10:30 +0000 Date: Sun, 16 Jan 2005 09:10:30 +0000 From: Dick Davies To: PostgreSQL Admin Subject: Re: PAM ldap Message-ID: <20050116091030.GC26970@lb.tenfour> Reply-To: Dick Davies References: <782D2A81EC812642B857B03B506E0B4432637A@granite.omni.imsweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <782D2A81EC812642B857B03B506E0B4432637A@granite.omni.imsweb.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.632 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: * X-Archive-Number: 200501/167 X-Sequence-Number: 16026 * Kavan, Dan (IMS) [0149 18:49]: > > Hi, I'm running postgresql 8.0.rc5 on SUSE. > I have the pg_hba.conf file configured with > local all smith ident sameuser > host all smith ident sameuser > > The way authentication works with that is that configuration is that if > I'm logged in as smith with my company ldap server I can get in, but if > I'm not directly logged in as smith, I can't get in. Having the word > pam in this file at all causes an error. I'd like to use pam so > postgres could do it's own ldap/pam lookups, but I keep getting an error > that it doesn't know what pam is. I see in the logs that the pam server > starts, but I still get an error. You didn't show the broken config, but assuming it's something like # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD hostssl all all 127.0.0.1 255.255.255.255 pam then perhaps you don't have pam support built into postgres? > /etc/pam.d/postgresql > auth required pam_unix2.so nullok > account required pam_unix2.so This is going to do unix auth, obviously, so you'll need to s/unix/ldap/ on that... -- 'You may need to metaphorically make a deal with the devil. By 'devil' I mean robot devil and by 'metaphorically' I mean get your coat.' -- Bender Rasputin :: Jack of All Trades - Master of Nuns