On 1/21/2017 1:37 PM, Stephen Frost wrote:
* PAWAN SHARMA (er.pawanshr0...@gmail.com) wrote:
So, there is no solution for my first question, we need if users enter the
wrong password more than 5 times than their account gets locked and then
only DBA will unlock this account.
I understood the qu
* Thomas Kellerer (spam_ea...@gmx.net) wrote:
> Stephen Frost schrieb am 21.01.2017 um 22:37:
> >>So, there is no solution for my first question, we need if users enter the
> >>wrong password more than 5 times than their account gets locked and then
> >>only DBA will unlock this account.
> >
> >I u
Stephen Frost schrieb am 21.01.2017 um 22:37:
So, there is no solution for my first question, we need if users enter the
wrong password more than 5 times than their account gets locked and then
only DBA will unlock this account.
I understood the question and there is an answer- use PAM.
What
Pawan,
Please be sure to include the mailing list on replies, so others can
benefit from the discussion. Also, please reply in-line, as I do below,
instead of top-posting.
* PAWAN SHARMA (er.pawanshr0...@gmail.com) wrote:
> So, there is no solution for my first question, we need if users enter t
Pawan,
* PAWAN SHARMA (er.pawanshr0...@gmail.com) wrote:
> 1. How can we set user account block feature after max number of
> invalid password entries?
There are ways to accomplish this, but they're unfortunately
complicated. In the past, I've implemented these kinds of requirments
by using the
On Sun, Jan 22, 2017 at 12:32:21AM +0530, PAWAN SHARMA wrote:
> I have few question regarding Postgres security.
>
> 1. How can we set user account block feature after max number of
> invalid password entries?
> 2. How can we use SSL encryption in Postgres on Linux environment?
> 3. How can we
