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 1p6C7S-0000vW-3B for pgsql-admin@arkaria.postgresql.org; Fri, 16 Dec 2022 14:55:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p6C7Q-0000ke-UH for pgsql-admin@arkaria.postgresql.org; Fri, 16 Dec 2022 14:55:24 +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 1p6C7Q-0000kT-Gf for pgsql-admin@lists.postgresql.org; Fri, 16 Dec 2022 14:55:24 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p6C7J-0005KV-Ki for pgsql-admin@lists.postgresql.org; Fri, 16 Dec 2022 14:55:23 +0000 Received: by mail-ej1-x634.google.com with SMTP id x22so6661189ejs.11 for ; Fri, 16 Dec 2022 06:55:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=4+zs/tiyrQu/djGOOiTaT8VgiTvh/4NhWzm0oaCdNAw=; b=GE7KL7TwweDYxrIrcbWjHTyToThCcGvvj2zpX7bKamuE4HGpUQAiFOp8b3v1nDbN6H s0JxiKd+nfq9EE+RAUAUvDQSoHVvAJwUcFsu7oWcRA8/CSOXHzHb1PqflKombcU4jxLU XhZa2f5WwWTdyFo9g66YugdmpfoCw4w3olzF+H620nPTXtLc1L8Y01uihET7yBU2QJHM 1nz89eqOqEoQn7DxlxeTeDOXJOPFxx5mupjwZxjHJ5Qm2gf8wZWesxpQyP0yrYai9+WR uiB4aGZRbhwkBU1dMhH6VwVkOtx0eQZVyBwiFxnjCm6Pi+Ytzvx/ktDiupgNYsmyAfUx 8fFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=4+zs/tiyrQu/djGOOiTaT8VgiTvh/4NhWzm0oaCdNAw=; b=q+FVSs6D3NHf3S2XD9ETAujPgHxutglZjyhXF/JYPq3XEfIepo3oOy+xmf78fDaCdw Zr5+HOjby642Ntw02yvQ9T/5j1xeukRLic59i6a6tRFVEHrcgUrBkPz+IH8Qp4ZNyLsR HAVnvKMwX8xpKaTWCcMIX0zGnofg6zIe+WWsSpI/7/GMMV4CKijLUJWicQ+Wr7zdIfjQ oXSRz1leNNs2qUJ+/hbOK1+NNvZ4keyV+z6CyrnmSLzRr56lT49vTbcci4ZnEj90jq3V iE+535O9Uk3m2USersPkht1Z+c4lByeQ4hi4ULfp2XyGBYBjUOE0v1a4u6iNdFkA3TL2 8NWA== X-Gm-Message-State: ANoB5pkpjp5XEp9EB4BP+zMmtfVsRWRq1tsWwUk76rp+liFVIXovVdTP L9249b0g5E885HqrLyl4MJdDyg== X-Google-Smtp-Source: AA0mqf4E+biFemst/EWEKodMgHJNBCTcrDdacirIlVIzTvxL9XxaqjmGVll+TXh+ENwo4GuOaICVDg== X-Received: by 2002:a17:906:382:b0:7c1:7532:b9bd with SMTP id b2-20020a170906038200b007c17532b9bdmr29990494eja.54.1671202514751; Fri, 16 Dec 2022 06:55:14 -0800 (PST) Received: from localhost.localdomain (178-190-174-218.adsl.highway.telekom.at. [178.190.174.218]) by smtp.gmail.com with ESMTPSA id f1-20020a17090631c100b007c07b23a79bsm920615ejf.213.2022.12.16.06.55.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 16 Dec 2022 06:55:14 -0800 (PST) Message-ID: <2192ed923b577ce4a8a90479c7ed1c97f7a6523d.camel@cybertec.at> Subject: Re: Password complexities in Postgres v14.6 From: Laurenz Albe To: Daulat , pgsql-admin Date: Fri, 16 Dec 2022 15:55:09 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2022-12-16 at 17:57 +0530, Daulat wrote: > Any idea, how we can set some Password complexities in postgres for user password. Like, we can create profiles in Oracle. > I am looking to set the Password complexities  (one parameter from each line item has to be complied to): > Default password age for users: 90 days. > Password first letter will be alphabetic in uppercase. > English uppercase characters (A through Z) > English lowercase characters (a through z) > Base 10 digits (0 through 9) > Non-alphabetic characters ~" &_-+='! (){}[):;"'<>,.?/ !@#$%* > Password Minimum Length 8 character There is no reliable way to do this in PostgreSQL, since the server typically never sees the clear text password. You should consider using one of the other authentication methods like "ldap" and enforce the policy on the LDAP server. Yours, Laurenz Albe