pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael.Dietrich@swisscom.com
To: sfrost@snowman.net
Cc: pgsql-admin@lists.postgresql.org
Subject: AW: Connect to db denied for superuser inherited by group
Date: Tue, 20 Mar 2018 08:29:43 +0000
Message-ID: <214530c2d4cb438ca204bd2a3b5b4747@swisscom.com> (raw)
In-Reply-To: <20180316134234.GE2416@tamriel.snowman.net>
References: <b93d9993e79545ffaa54d440a6f4383f@swisscom.com>
	<9cd041b2b19143758e4f4d8a752421c5@swisscom.com>
	<20180316134234.GE2416@tamriel.snowman.net>

What I've done

CREATE ROLE superrole WITH  NOLOGIN  SUPERUSER ..;	
CREATE USER nosuperuser WITH LOGIN NOSUPERUSER INHERIT ..;
GRANT superrole TO nosuperuser WITH ADMIN OPTION;
REVOKE CONNECT ON DATABASE nonpublicdb FROM public ;

psql -d postgres -U nosupuser

postgres=# set role superrole;

postgres=# \c nonpublicdb
FATAL:  permission denied for database " nonpublicdb "
DETAIL:  User does not have CONNECT privilege.

I expect that the connection to the database is allowed since a role with superuser is used.  (I don't' expect any difference between using a role (including superuser) or a user (including superuser).)

Postgres Version: PostgreSQL 9.5.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4), 64-bit

Regards --Michael


-----Ursprüngliche Nachricht-----
Von: Stephen Frost [mailto:sfrost@snowman.net] 
Gesendet: Freitag, 16. März 2018 14:43
An: Dietrich Michael, INI-ONE-CIS-GSV-MFS <Michael.Dietrich@swisscom.com>
Cc: pgsql-admin@lists.postgresql.org
Betreff: Re: Connect to db denied for superuser inherited by group

Greetings,

* Michael.Dietrich@swisscom.com (Michael.Dietrich@swisscom.com) wrote:
> Unexpected behavior when trying to connect to a database. Facts:
> 1) The privilege to connect to the database was revoked from public.
> 2) User without superuser privileges uses a role with superuser rights 
> (usage confirmed with SHOW current_role.)

Please provide more details about what this step #2 actually means.

> 3) Unecpected Message: FATAL: permission denied for database "db" DETAIL: User does not have CONNECT privilege.

Details about exactly what you're doing to connect here would be helpful.

> After granting one of the listed privileges it is working as expected.
> 1) granting superuser to user
> 2) granting connect to db for user
> 3) granting connect to db to group
> 3) granting connect to db to public
> 
> What am I missing?  --Michael

CONNECT privileges are needed to be able to connect to the database, so it's not surprising that you needed to GRANT them to the user after REVOKE'ing them from PUBLIC.  What's not clear is what you're actually trying to do and what you're expecting to work that apparently isn't.

Thanks!

Stephen




view thread (2+ messages)  latest in thread

Message-ID: <214530c2d4cb438ca204bd2a3b5b4747@swisscom.com>
Permalink:  ../214530c2d4cb438ca204bd2a3b5b4747@swisscom.com/
Also on:    postgresql.org/message-id/214530c2d4cb438ca204bd2a3b5b4747@swisscom.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: Michael.Dietrich@swisscom.com, sfrost@snowman.net, pgsql-admin@lists.postgresql.org
  Subject: Re: AW: Connect to db denied for superuser inherited by group
  In-Reply-To: <214530c2d4cb438ca204bd2a3b5b4747@swisscom.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox