Re: Moving pgadmin4.db to a new server

Hi Jan,

Try this,
1) Remove all the existing session data. For that, shut down the server, go
to sessions directory just beside the db file and remove all the files in
it.
2) Go to browser and clean all the cache.
3) Start pgAdmin4 and open a new window.
Let us know if this works.

On Sun, Oct 20, 2019 at 12:51 PM Jan Birk <jan(dot)g(dot)birk(at)gmail(dot)com> wrote:

> Hi and thanks for your efforts and time
>
> søn, 20 10 2019 kl. 11:45 +0530, skrev Aditya Toshniwal:
> > How did you copy the .db file ?
> > Did you copy first and then started pgAdmin or started first and then
> copied.
> > When pgAdmin4 starts, it checks the schema version of .db file and
> applies the
> > migrations till the current version.
>
>
> We did copy and then started. That's explain why the schema *seems* to be
> ok :-)
>
> We haven't moved the production site yet. But every thing in out test
> looks ok
> expect the passwords.
>
> Not knowing python (just grep) it seems that the SALT is auto generated in
> config-database??
>
> ../migrations/versions/xxxxxx_.py
> ..
>
> 114 current_salt = getattr(
> 115 config, 'SECURITY_PASSWORD_SALT',
> base64.urlsafe_b64encode(
> 116 os.urandom(32)
> 117 ).decode()
> 118
> )
> ..
>
> Could it be a workaround to re-initialize (re-install) pgadmin having
> current_salt equals the old one ???
>
> Best
>
> Jan
>
>

--
Thanks and Regards,
Aditya Toshniwal
Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"