public inbox for [email protected]help / color / mirror / Atom feed
query to show locked / disabled users? 4+ messages / 3 participants [nested] [flat]
* query to show locked / disabled users? @ 2022-04-14 19:19 Sbob <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Sbob @ 2022-04-14 19:19 UTC (permalink / raw) To: Pgsql-admin <[email protected]> I have a client that says there were break in attempts and many db users are now disabled / locked because of too many wrong pw attempts. Is there a select that will show these users? Thanks in advance ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: query to show locked / disabled users? @ 2022-04-14 19:24 David G. Johnston <[email protected]> parent: Sbob <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: David G. Johnston @ 2022-04-14 19:24 UTC (permalink / raw) To: Sbob <[email protected]>; +Cc: Pgsql-admin <[email protected]> On Thursday, April 14, 2022, Sbob <[email protected]> wrote: > I have a client that says there were break in attempts and many db users > are now disabled / locked because of too many wrong pw attempts. Is there > a select that will show these users? > > You can look at pg_roles. David J. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: query to show locked / disabled users? @ 2022-04-14 19:34 Tom Lane <[email protected]> parent: David G. Johnston <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Tom Lane @ 2022-04-14 19:34 UTC (permalink / raw) To: David G. Johnston <[email protected]>; +Cc: Sbob <[email protected]>; Pgsql-admin <[email protected]> "David G. Johnston" <[email protected]> writes: > On Thursday, April 14, 2022, Sbob <[email protected]> wrote: >> I have a client that says there were break in attempts and many db users >> are now disabled / locked because of too many wrong pw attempts. Is there >> a select that will show these users? > You can look at pg_roles. That probably won't help much, because Postgres has no built-in mechanism for disabling users on the basis of "too many wrong pw attempts". Whatever has decided that must be external to Postgres (perhaps getting accessed via LDAP or PAM?) and you're going to have to look at its state. In short, there's not enough info here for us to offer any useful advice. regards, tom lane ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: query to show locked / disabled users? @ 2022-04-14 19:36 Sbob <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Sbob @ 2022-04-14 19:36 UTC (permalink / raw) To: Tom Lane <[email protected]>; David G. Johnston <[email protected]>; +Cc: Pgsql-admin <[email protected]> Got it, thanks On 4/14/22 13:34, Tom Lane wrote: > "David G. Johnston" <[email protected]> writes: >> On Thursday, April 14, 2022, Sbob <[email protected]> wrote: >>> I have a client that says there were break in attempts and many db users >>> are now disabled / locked because of too many wrong pw attempts. Is there >>> a select that will show these users? >> You can look at pg_roles. > That probably won't help much, because Postgres has no built-in > mechanism for disabling users on the basis of "too many wrong pw > attempts". Whatever has decided that must be external to Postgres > (perhaps getting accessed via LDAP or PAM?) and you're going to have > to look at its state. In short, there's not enough info here for > us to offer any useful advice. > > regards, tom lane ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2022-04-14 19:36 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-04-14 19:19 query to show locked / disabled users? Sbob <[email protected]> 2022-04-14 19:24 ` David G. Johnston <[email protected]> 2022-04-14 19:34 ` Tom Lane <[email protected]> 2022-04-14 19:36 ` Sbob <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox