MIME-Version: 1.0
References: 
 <CANNh3aX1ZdOrXZx_92=8QJc0ZzBYYghCaAjRLkOJ69=UGrftvA@mail.gmail.com>
In-Reply-To: 
 <CANNh3aX1ZdOrXZx_92=8QJc0ZzBYYghCaAjRLkOJ69=UGrftvA@mail.gmail.com>
From: Dave Page <dpage@pgadmin.org>
Date: Thu, 27 Jun 2019 11:15:52 -0400
Message-ID: 
 <CA+OCxoy28r9zWG5u1jagf-6B4274H0A5P4iU_rJ4jr6n7t-O8A@mail.gmail.com>
Subject: Re: passwords enabled by default
To: Andrew Coleman <penguincoder@gmail.com>
Cc: pgadmin-hackers <pgadmin-hackers@lists.postgresql.org>,
	Syed Fahar Abbas <fahar.abbas@enterprisedb.com>
Content-Type: multipart/alternative; boundary="000000000000e6055f058c4fa381"
Precedence: bulk

--000000000000e6055f058c4fa381
Content-Type: text/plain; charset="UTF-8"

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 <penguincoder@gmail.com>
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

--000000000000e6055f058c4fa381
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Fahar, can you verify that the Password File option w=
orks as expected (or not) in a non-containerised environment? It should *no=
t* require PGPASSFILE to be set (because that&#39;s basically what it shoul=
d be doing for us).</div><div><br></div><div>Thanks.</div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jun 27, 2019 at=
 8:27 AM Andrew Coleman &lt;<a href=3D"mailto:penguincoder@gmail.com">pengu=
incoder@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div>Recently, while testing my changes t=
o entrypoint.sh in Docker, I noticed that you cannot import or export passw=
ords via the servers.json file. You can get around this by setting the Pass=
File option in servers.json, but that still doesn&#39;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.</div><div><br></div><=
div>To clarify, I know how many servers I want to connect to and how to fin=
d 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 c=
onnect to the servers without user intervention.</div><div><br></div><div>T=
he presence of the pgpass file and the reference to that file in the server=
s.json was not enough to allow pgadmin4 to connect to the servers, I also h=
ad to set `PGPASSFILE` in my Helm chart to make this work.</div><div><br></=
div><div>This seems like another good ticket, no? I know where to add them =
and I&#39;ll put a patch in place, but I could sure use a little bit of gui=
dance 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?</div=
><div><br></div><div>Thanks,</div><div>Andrew<br></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Dave Page<br>Blog: <a href=3D"http://pgsnake.blo=
gspot.com" target=3D"_blank">http://pgsnake.blogspot.com</a><br>Twitter: @p=
gsnake<br><br>EnterpriseDB UK: <a href=3D"http://www.enterprisedb.com" targ=
et=3D"_blank">http://www.enterprisedb.com</a><br>The Enterprise PostgreSQL =
Company<br></div></div>

--000000000000e6055f058c4fa381--