Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hiyXS-0003Dn-Si for pgadmin-hackers@arkaria.postgresql.org; Thu, 04 Jul 2019 10:00:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hiyXR-0002bm-NA for pgadmin-hackers@arkaria.postgresql.org; Thu, 04 Jul 2019 10:00:25 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hiyXR-0002bf-BF for pgadmin-hackers@lists.postgresql.org; Thu, 04 Jul 2019 10:00:25 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hiyXN-0003de-JQ for pgadmin-hackers@lists.postgresql.org; Thu, 04 Jul 2019 10:00:24 +0000 Received: by mail-lj1-x229.google.com with SMTP id m23so5530674lje.12 for ; Thu, 04 Jul 2019 03:00:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uFz3CmA8YkQjIQqFPjlJ+QcbbjnT2dCeh26zJzrLeH0=; b=zukYD/RKN/mqL0RAlML/qUEOZQV3nAr0PL6jedi5e0o4foMMUmdIBasIVusUoYNSEF RzitNJHqL1dMUor2vayrDy1xxa5pRaxQ1QXpo4fjDu11bMWJXRoo4iL29XyVLngGskSG ZiJGIB69dNqGmZP4AeGi/g+UnIdW2ztDFA70PmV2A9+DGDlcRMK86xKh1TiwMjLlrONB FI+pYhBeE9NYNUgXqxojwfWguZ4uGmqk2C/McwO0PWck78lbPwwhwl5zGKV0O1rRwpr8 OAjrk8IC+pvzUoJ41qDVj9wD7rjjVFN5UhXV6Etvm0QoSC9Fywc3N6I6TcVyNPmlQ9Bb Xjrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uFz3CmA8YkQjIQqFPjlJ+QcbbjnT2dCeh26zJzrLeH0=; b=KqwcScsi2tH8/YCM7jd75o27g9I28rEyZqyd+OU8AEKnrw6Y2UK0uaxjBuYHmRvrQP kgxV3ZCEZVrg1/kHvIdi/NLEdqd//ECwzNNSfmmef3hTIUdBIskYtbOCGJH10PeCqgyq WVlripbraJ1a2OmO8zdfMtiTEOTxwLVSSI9GxPZA9HPa6QD11RCbTt0bIVru4SW18K+j 3SkkWpg5i5uMoafgr1Su/mk6HAPS0FRzLXls/teD9/5tQ8RmQBvvtz5M4HDK48LBPGQw vVZE533Ulz83bE0vwfRbM4QGzdgfYxrnyXMGtZ4G4MC86Io3NpXHeDLGtMepdusMFvpW wNsQ== X-Gm-Message-State: APjAAAXftmo5tOM17AmcLLMHcAWewnKkISYpDJJfG+24KG2BVMq0l0ZG 726BIDyB4sIz0wg00w618nFBNCCMWPQgnfsom2Uy0Q== X-Google-Smtp-Source: APXvYqxli4qPL2NZL5HUTv4gTt553yTSxLRKqDcBz1rYRyF00soAPlZvtyTcABL8izLS10w0jj8O9gMufEtkp8y8jM4= X-Received: by 2002:a2e:9a49:: with SMTP id k9mr24244122ljj.78.1562234420649; Thu, 04 Jul 2019 03:00:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Fahar Abbas Date: Thu, 4 Jul 2019 15:00:09 +0500 Message-ID: Subject: Re: passwords enabled by default To: Dave Page Cc: Andrew Coleman , pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000b2f5e3058cd80b1c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000b2f5e3058cd80b1c Content-Type: text/plain; charset="UTF-8" Yes Dave it's working as expected. On Thu, Jun 27, 2019 at 8:16 PM Dave Page wrote: > Fahar, can you verify that the Password File option works as expected (or > not) in a non-containerised environment? It should *not* require PGPASSFILE > to be set (because that's basically what it should be doing for us). > > Thanks. > > On Thu, Jun 27, 2019 at 8:27 AM Andrew Coleman > wrote: > >> Recently, while testing my changes to entrypoint.sh in Docker, I noticed >> that you cannot import or export passwords via the servers.json file. You >> can get around this by setting the PassFile option in servers.json, but >> that still doesn't work correctly. For me to make this work, I had to also >> set the `PGPASSFILE` to the full path location of the pgpass file generated >> for me by Helm. >> >> To clarify, I know how many servers I want to connect to and how to find >> their passwords in Kubernetes via their secret, and I use Helm to stitch >> all of that together into a pgpass file that psql and pgadmin4 can use to >> connect to the servers without user intervention. >> >> The presence of the pgpass file and the reference to that file in the >> servers.json was not enough to allow pgadmin4 to connect to the servers, I >> also had to set `PGPASSFILE` in my Helm chart to make this work. >> >> This seems like another good ticket, no? I know where to add them and >> I'll put a patch in place, but I could sure use a little bit of guidance on >> the copy portion of the documentation. I know why it works for me, but >> would anyone conceivably use this in a non-Dockerized deployment? >> >> Thanks, >> Andrew >> > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > -- Fahar Abbas QMG EnterpriseDB Corporation Phone Office: +92-51-835-8874 Phone Direct: +92-51-8466803 Mobile: +92-333-5409707 Skype ID: *live:fahar.abbas* Website: www.enterprisedb.com --000000000000b2f5e3058cd80b1c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes Dave it's working as expected.

On Thu, Jun 27, = 2019 at 8:16 PM Dave Page <dpage@pg= admin.org> wrote:
Fahar, can you verify that the Password Fi= le option works as expected (or not) in a non-containerised environment? It= should *not* require PGPASSFILE to be set (because that's basically wh= at it should be doing for us).

Thanks.

On Thu, Jun = 27, 2019 at 8:27 AM Andrew Coleman <penguincoder@gmail.com> wrote:
Recentl= y, while testing my changes to entrypoint.sh in Docker, I noticed that you = cannot import or export passwords via the servers.json file. You can get ar= ound this by setting the PassFile option in servers.json, but that still do= esn't work correctly. For me to make this work, I had to also set the `= PGPASSFILE` to the full path location of the pgpass file generated for me b= y Helm.

To clarify, I know how many servers I want= to connect to and how to find their passwords in Kubernetes via their secr= et, and I use Helm to stitch all of that together into a pgpass file that p= sql and pgadmin4 can use to connect to the servers without user interventio= n.

The presence of the pgpass file and the referen= ce to that file in the servers.json was not enough to allow pgadmin4 to con= nect to the servers, I also had to set `PGPASSFILE` in my Helm chart to mak= e this work.

This seems like another good ticket, = no? I know where to add them and I'll put a patch in place, but I could= sure use a little bit of guidance on the copy portion of the documentation= . I know why it works for me, but would anyone conceivably use this in a no= n-Dockerized deployment?

Thanks,
Andrew<= br>


--
Dave Page
Blog: <= a href=3D"http://pgsnake.blogspot.com" target=3D"_blank">http://pgsnake.blo= gspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.comThe Enterprise PostgreSQL Company


--
Fahar Abbas
QMG
EnterpriseDB Corporation
Phone = Office: +92-51-835-8874
Phone Direct: +92-51-8466803
Mobile: +92-333-= 5409707
Skype ID: live:fahar.abbas
Website: www.enterprisedb.com
<= /div>
--000000000000b2f5e3058cd80b1c--