Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAucu-0003Xe-2L for pgsql-admin@arkaria.postgresql.org; Fri, 21 Jan 2022 14:10:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nAucs-0002RD-VN for pgsql-admin@arkaria.postgresql.org; Fri, 21 Jan 2022 14:10:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAucs-0002R0-Gq for pgsql-admin@lists.postgresql.org; Fri, 21 Jan 2022 14:10:50 +0000 Received: from mail-qv1-xf2b.google.com ([2607:f8b0:4864:20::f2b]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nAucn-0000ju-3Y for pgsql-admin@lists.postgresql.org; Fri, 21 Jan 2022 14:10:49 +0000 Received: by mail-qv1-xf2b.google.com with SMTP id a8so10534358qvx.2 for ; Fri, 21 Jan 2022 06:10:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=SkdYBjZiVQ81kWJgevIjjmoGNV35ttBY+uvqIavCdeg=; b=mYu+3z0K4RXIyfPHwnsq3FycY7M95WZeXGBN8X4g3yJJIevzf3YR1Nt5K5JSvMbEyz eUW41505uEc1k6DNSgVTZc0FKGpaDN95SmMPCw8EmTYqVUDmiI+ddsyp4PUsK8GgTgks uaAnK8n2oYgzUPd9YOqPZfBlO05tLwFn+t8H2w0ID8Zs62kuQPFTJkdVSVlisZJ5gNbn ivshr3LMASKKgqW/WUrmh1DLSiEBTlckqLMhH8xDeWZGyENr+mUd6mYH1YgDsS+aWX6k Sa2mjPzpyZcdnnu9g4SqB9gHh7kJ27CLgr11o6AB2AX25Oz0oC2jlBERv5G3OSaQvGf+ XaQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=SkdYBjZiVQ81kWJgevIjjmoGNV35ttBY+uvqIavCdeg=; b=y4ldhR+dbCi+Wj8ID8q6X9rmq/PfAn0r7B3X8lXSB9gDufiwLXZ26Gzx68VXHBbGtm kMCgO9oXszKfhyT44+y+OC+ZatM85xoGfi9fBsMiC2WiJk5kqS9idOVplXmjNPy8UYgq 0QhQzMbN5oT/xiH3OguX9lr1UBAwDvG0oIERvkm2RrB/hnqd5QQ2W/wEqu4spZ5NqoxC pHe/SJ0eNqjt97gDlUgO0ryLTrhvMxF1yJH2mKGGP0Fh5fypXzjUKhfIQW4tySv560/R zmWCDyKqdtxrppkpeOp3OqPrEOo9mssb0IWTtn0gbgu4A2F3l+frVl2OJNGOAvjNxzKX 1uBQ== X-Gm-Message-State: AOAM531EVMLNQHwW/2yU/Vd/jycrof3CzFLCLxceWc6sBypdMVDvF8Lr i5pdx46jKemvth3EWzHsgD3pCXJ0VT0= X-Google-Smtp-Source: ABdhPJxDkXHZ87rxd/rThKNoXYCMttPMZzxBmjhIcZqxP/vOi/xHEz465aIOt6WSpgD3pDDmbYqSdw== X-Received: by 2002:a05:6214:2386:: with SMTP id fw6mr3663999qvb.131.1642774243721; Fri, 21 Jan 2022 06:10:43 -0800 (PST) Received: from [192.168.2.100] (pool-72-79-19-93.nwrknj.east.verizon.net. [72.79.19.93]) by smtp.gmail.com with ESMTPSA id b13sm2982606qkh.134.2022.01.21.06.10.42 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 21 Jan 2022 06:10:43 -0800 (PST) Content-Type: multipart/alternative; boundary="------------L7Zb8tVqZ0dNqdEfB8lV0cRl" Message-ID: Date: Fri, 21 Jan 2022 09:10:42 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: Password authorization Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: From: Mladen Gogala In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------L7Zb8tVqZ0dNqdEfB8lV0cRl Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 1/20/22 09:25, Laurenz Albe wrote: > It is not quite clear what you mean, but I assume you want password complexity rules, > and you want to force users to change their password after a while. > > You cannot do any of that with passwords in the database; the best you can > do is set an expiration time for the user's ability to log in. Actually, you can. There is the standard "passwordcheck" module described in the documentation: https://www.postgresql.org/docs/current/passwordcheck.html You would have to do some C programming, but it's very possible. Regards -- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com --------------L7Zb8tVqZ0dNqdEfB8lV0cRl Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
On 1/20/22 09:25, Laurenz Albe wrote:
It is not quite clear what you mean, but I assume you want password complexity rules,
and you want to force users to change their password after a while.

You cannot do any of that with passwords in the database; the best you can
do is set an expiration time for the user's ability to log in.

Actually, you can. There is the standard "passwordcheck" module described in the documentation:

https://www.postgresql.org/docs/current/passwordcheck.html

You would have to do some C programming, but it's very possible.

Regards

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
--------------L7Zb8tVqZ0dNqdEfB8lV0cRl--