Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1to1vn-0052OV-Uc for pgsql-general@arkaria.postgresql.org; Fri, 28 Feb 2025 15:05:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1to1vo-008P1x-Vp for pgsql-general@arkaria.postgresql.org; Fri, 28 Feb 2025 15:05:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1to1vo-008P1m-L1 for pgsql-general@lists.postgresql.org; Fri, 28 Feb 2025 15:05:39 +0000 Received: from mail-ej1-x62a.google.com ([2a00:1450:4864:20::62a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1to1vl-000BWu-1A for pgsql-general@postgresql.org; Fri, 28 Feb 2025 15:05:38 +0000 Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-abb79af88afso413412166b.1 for ; Fri, 28 Feb 2025 07:05:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740755136; x=1741359936; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=/c1nSV04B6ThH5L5lqvDo8/1jKFjTowo3indbsLpDvA=; b=HaEPZgB9EUpQVWIDpFhzlGNXEuJ7VHCFx2azcymUVo6CmH5qQ8yeg4oVGfAT0LOFQo PNykpC6cEolvEaOAcCr5VIDTFspmh0mTBZh5HCYrRA4EujATS/z+ha2hyq8+hPOJjvVw IsvtU4I2N0GyFMbb3uEbQ+TODGreJA0bFqhNsAztANwDiETjIr+eOn2UdUSW6zlnnLYP u8WjykZWRpZjJJIK+TZH64obl4704ZLFk1ZfdciVZ3w1+pgepN0DC2wTdeczmtVmh2Ka QjdwgY+xHeH27/RBJnGH+3QbVdnDTM2PIsM9D3EGjK4OaLcQyFP7H7So91E0Uwnrz901 HWvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740755136; x=1741359936; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=/c1nSV04B6ThH5L5lqvDo8/1jKFjTowo3indbsLpDvA=; b=tzJdukSNe1cFpFFNid29jHj9t491NcRzNFr+oSZKyNhgcfCWxkvE0eAAR5VuglA6zt YAOO4dtZ9z6Y4Nezh5S+TgBFhkXlroRH8Zu7SAoGlLjGwU0WaKCVmR2cIL1+omf2uxPp zKB7l8M5Z2xes2fasMEPEsGPuZ5JtcuXsZXpAXz8SdZNUyOp0SW7I3oATb39HoqKcOoD FaUB8yWsll0nw/WlX+BAnNSQnRzm9MPIGFIi8tjbPYFwGjieudKtle+etqdJStOqRvI0 GsguAGp4A8GBn5a44B5wNZATYY9yofi9ECnH2iStxtSGCzccwp3UweeH+aBF5Gm80Yq/ Ngdw== X-Gm-Message-State: AOJu0YzVgZ2TeRCFTAHLIz6zxTqb1TpPjsQrTh1Ljw/8+XEalEVO6BUQ u9rCzwbT6y+vv2JuURzkjSP4wtT09VijFqz+6sIZD7J9kMYrShT0Hht7vf+GRC+xRaKpOiglhFi xMFX1v4kneLhbHECnwRdR1WBuuvcmf2slXs4= X-Gm-Gg: ASbGnctNZvL6MIDzWkd+bIrlk8sdMabLHiB+9DgCw0hWWEiOpauT6XwSvlcmypDfNDx 3u7HbrrMJqsS/Q2+cG5NdL2gIeBpgvHBIMJBoaIhzV9/puNioX+R7N4j2WWjteqKeHRU2cgAyIT nqrvEksitZF2tgzfEYeGAqBKxovyA= X-Google-Smtp-Source: AGHT+IGUr5hRtCJ16GNNWgcK4MLmLg/9lsbew/3EDO3R9g+9ijHlIDZCmX7VxmUeCHC8SxLt725FyJVw4XmEfvnzHho= X-Received: by 2002:a17:907:dac:b0:ab9:63bd:91be with SMTP id a640c23a62f3a-abf25f8fe96mr343872066b.3.1740755133316; Fri, 28 Feb 2025 07:05:33 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Alexander Farber Date: Fri, 28 Feb 2025 16:05:20 +0100 X-Gm-Features: AQ5f1Jru1HzUc2OxIf7oXjK35GpCtZxDISPeiNBV7sGDVfat8brd1bPzRsklfgY Message-ID: Subject: Re: Azure Database for PostgreSQL flexible server: password authentication failed To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000005cc9f2062f3523ba" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005cc9f2062f3523ba Content-Type: text/plain; charset="UTF-8" Ah my team mate has spotted the error for me. And it paid off, that he has no experience with PostgreSQL yet :-) Because the admin user for Azure Database for PostgreSQL flexible server is not "postgres" but "postgresql" Now the connection from a container in AKS works for me: $ psql "postgresql://postgresql:password12345!!@ 172.21.32.4:5432/postgres?sslmode=require" psql (17.4, server 16.6) SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off, ALPN: none) Type "help" for help. postgres=> I must find now how to add a non-super user to it next. Best regards Alex --0000000000005cc9f2062f3523ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ah my team mate has spot= ted the error for me.

And it paid off, that he has no experience wit= h PostgreSQL yet :-)

Because the admin user for=C2=A0Azure Database = for PostgreSQL flexible server is not "postgres" but "postgr= esql"

Now the connection from a container in AKS works for me:<= br>
$ psql "postgresql://postgresql:password12345!= !@172.21.32.= 4:5432/postgres?sslmode=3Drequire"
psql (17.= 4, server 16.6)
SSL connection (protocol: TLSv1.3, ci= pher: TLS_AES_256_GCM_SHA384, compression: off, ALPN: none)
Type "help" for help.
=C2=A0
=
postgres=3D>

I must find now how to add a non-su= per user to it next.

Best regards
Alex

--0000000000005cc9f2062f3523ba--