Postgres Pro
Downloads
Home   >   mailing lists

Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires. - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires.
Date
Msg-id CA+OCxoyghzW2OJyxC2MpyHX3=T=pSJm1s5nxG8qZO_e6Hm08SA@mail.gmail.com
Whole thread Raw
In response to Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires.  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
Responses Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires.
List pgadmin-hackers
Tree view


On Thu, Jan 14, 2021 at 8:18 AM Akshay Joshi <akshay.joshi@enterprisedb.com> wrote:
Thanks, patch applied.

On Thu, Jan 14, 2021 at 11:28 AM Nikhil Mohite <nikhil.mohite@enterprisedb.com> wrote:
Hi Team,

Please find the attached patch for RM-6120: Adding/updating user should not allow to add an older date in account expires.
Added UI validation if a user enters the account expiration date manually.

I think this needs to be reverted (and the UI fixed to allow an older date to be selected).

Selecting a past expiry date is a perfectly valid way to create an account that is effectively locked, for example, to allow pre-creation of roles for staff that are yet to join.

PostgreSQL doesn't prevent this - why should we?

--  
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: http://www.enterprisedb.com

pgadmin-hackers by date:

Previous
From: Akshay Joshi
Date:
Subject: Re: [pgAdmin4][Patch] - RM 5457 - Kerberos Authentication - Phase 1
Next
From: Dave Page
Date:
Subject: Re: Is there a mistake in line 22 of Make.bat?