Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gHnDY-0000v4-Vy for pgsql-performance@arkaria.postgresql.org; Wed, 31 Oct 2018 09:55:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gHnDX-0007kk-44 for pgsql-performance@arkaria.postgresql.org; Wed, 31 Oct 2018 09:55:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gHnDV-0007jj-Ko for pgsql-performance@lists.postgresql.org; Wed, 31 Oct 2018 09:55:14 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gHnDQ-0004gH-Ja for pgsql-performance@lists.postgresql.org; Wed, 31 Oct 2018 09:55:13 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 080E0220B1; Wed, 31 Oct 2018 05:55:07 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 31 Oct 2018 05:55:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=2uWPczuZdXPLa1d5jUYS+a7oa57 p2yO3kPlz96FMFyw=; b=kuMjoNVuvQVsDOamiY/HhwYMkUFbW0Ry8kYexlI+VyB WeQwn5VJ09UgNX3IyiYVVyyY7vPY7ifIoNqTblGZ4YABsrDD3KuiFQVOO2EZuaZ4 2K5pWC3eEbCm4G1qaSNf3ykWGRgya9X3TbAL4147vDMpBzbOimpZ+cXh+txcqv9M oxMMncdf5au3Xrv1BpAB0PkShL2vM52+KZWysKXygUMJPRe7wah9+DoUzI3ktdB2 SZJqxEWnNSkIqWxPd94tSp228UupDtWO7UVGYlTR/y6vx7xBZMzJPuNn7Pg+5F0Y MFT/LhktLZDad+DDFqtJJIuM7SNp+TV9EnA6Yn8OPdQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=2uWPcz uZdXPLa1d5jUYS+a7oa57p2yO3kPlz96FMFyw=; b=grj10rRGmWiSIQ1EZMx42q dEd/5BN0+YQU+V2yO7woMjc1yxmwcYLF0UgX6E+6VcU+xDF+OzjJe9nndU5fYV3U DVi8vwRFe789bccxABHGHQTc65J3vyo6NVCEQv3ACMBPeLxKrE93OqWHPzEgCDCT oLv3981paRc/dBC5cNOrYdTfqHDG48Tl6c2/7xInUqPe1crETF5zjsBC+8SNplVD H4flDK3gWW7CUt++A/rEPfgjeNa7lMj853WtYFhU1dgSwHRT8ZQ8db68RObzKP/f radFmnni5JOvJ96xpvwvji7PSaPvJkZkhXBlcG1jyoKjMfxaKqmdFTqN6IlvozxQ == X-ME-Sender: X-ME-Proxy: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 8FA66102ED; Wed, 31 Oct 2018 05:55:04 -0400 (EDT) Date: Wed, 31 Oct 2018 18:55:01 +0900 From: Michael Paquier To: "Joshua D. Drake" Cc: MichaelDBA , pgsql-performance@lists.postgresql.org Subject: Re: SCRAM question Message-ID: <20181031095501.GH7862@paquier.xyz> References: <5BD89A3D.5060108@sqlexec.com> <7460ee84-6c64-dcbc-4fc6-c88507ccb2ee@commandprompt.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Q59ABw34pTSIagmi" Content-Disposition: inline In-Reply-To: <7460ee84-6c64-dcbc-4fc6-c88507ccb2ee@commandprompt.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Q59ABw34pTSIagmi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 30, 2018 at 11:03:14AM -0700, Joshua D. Drake wrote: > On 10/30/18 10:51 AM, MichaelDBA wrote: >> I am using pgadmin4 version 3.4 with PG 11.0 and I get this error when I >> try to connect with scram authorization: >>=20 >> User "myuser" does not have a valid SCRAM verifier. >>=20 >> How do I get around this? And also how would I do this for psql? >=20 > You need to update the password using SCRAM I believe... >=20 > |See here: > https://paquier.xyz/postgresql-2/postgres-10-scram-authentication/| In order to do that, you would basically need to: 1) Switch password_encryption to 'scram-sha-256' in the server configuration. 2) Issue an ALTER ROLE command to update the password (likely it is better to use \password from psql as this would send a hashed password to the server, which relies on the server setting for password_encryption). 3) Make sure that pg_hba.conf is using properly scram-sha-256 where it should as authentication method. If you do not want to upgrade to SCRAM, it is of course possible to still remain with md5. -- Michael --Q59ABw34pTSIagmi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlvZe/UACgkQnvQgOdby QH0y9Q/+LlKCDggWd+DBH2va7119+RypYLFXssNH5NbDXDv/Lri0aEj4nINHfEfp VdXQmgti5GknEFqjDLYYCX5R82U/D7puwyvHfwZcRyap4Ze3UFyZiK0ApSb6pTS/ ti3Q/ztpE3B/L25eZlm6TP60v379rE7b7olSLG68U4Klnf4HposwYt88MK0i8xKx 4rsjiX+ypfFSBpMG4/HIz/BbewK3VVQLO4+Wd51ypQDC6GPljq+unoUU+IllAQv5 EbXYUXdDxsjWFojBXJ2f0rVOK16f6GE8NSEh4C3XJcOgbOTd/whTjBXaha4s34h5 Q++r/UUAqvCWt8L+vAoGxXtYoBpHBFdg6fdnkFFuvH7juJRNwOsF/7bohraPBMfo YfnZj3Ipk+PG4Z2a0qrGE1qEsMEVnjchHRi+zrWtsU53dcvuKKt4/b7yVNI3YkHr DMAhlsRss0nVxlcfv2/mo/h+yvTFbMpJ40bXjKm5o/kfufZa/MJfZj3nEzphvV/+ aOZ1KgNfUskVVmWzC5aEKVtcmuKd40ddZOn1HPmTF6tEc6lTRkdvInV88TP6GA1+ 5HLaTQJdVZjTUkUQuaf+QPt2yYU8pAyIsopvIs2GXqycZJDbz3MPhl3v2lJvoA16 tsGg3VtqRKMwH5p4x9MXqXEDg6DU8OHl8TWmehfR15vssA17So4= =yJSI -----END PGP SIGNATURE----- --Q59ABw34pTSIagmi--