X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3A479D7962 for ; Sat, 27 Aug 2005 10:31:18 -0300 (ADT) 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 28308-07 for ; Sat, 27 Aug 2005 13:31:15 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 26FCCD790E for ; Sat, 27 Aug 2005 10:31:12 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j7RDUpsA020597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 27 Aug 2005 07:30:54 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j7RDUp83059546; Sat, 27 Aug 2005 07:30:51 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j7RDUnW2059545; Sat, 27 Aug 2005 07:30:49 -0600 (MDT) (envelope-from mfuhr) Date: Sat, 27 Aug 2005 07:30:49 -0600 From: Michael Fuhr To: Jason Stone Cc: pgsql-admin@postgresql.org Subject: Re: password authentication with external passwd file Message-ID: <20050827133049.GA59344@winnie.fuhr.org> References: <20050827001001.L70885@treehorn.dfmm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050827001001.L70885@treehorn.dfmm.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 required=5 tests=[AWL=0.005] X-Spam-Level: X-Archive-Number: 200508/358 X-Sequence-Number: 18677 On Sat, Aug 27, 2005 at 01:31:25AM -0700, Jason Stone wrote: > I would like to know first, if I'm mistaken, or if external passwd files > are now specified in some other way, or must be enabled at compile time or > something like that; ie, am I doing something wrong? The 7.3 Release Notes have the following items: * Remove secondary password file capability and pg_password utility (Bruce) * Add variable db_user_namespace for database-local user names (Bruce) > If this feature is indeed no longer supported, is there some other way > that I can allow the same username to have different passwords on > different databases? See the documentation for db_user_namespace: http://www.postgresql.org/docs/8.0/static/runtime-config.html#RUNTIME-CONFIG-CONNECTION-SECURITY > The background is that this is a hosting environment, and each customer is > given one database to use however they want; different human users should > be able to create database users with the same username without > accidentally granting each other rights on their own databases. We > currently do this by maintaining a password file per user/database, and > letting users put whatever usernames and passwords they want into the > password file for their database. If you use db_user_namespace then you might have to provide an interface for users to manage the user names in their databases. One possibility would be to write a set of SECURITY DEFINER functions that execute the correct CREATE USER, DROP USER, etc. commands. -- Michael Fuhr