Hi On Fri, Jun 25, 2021 at 11:43 AM Jim Bacon <[email protected]> wrote:
> Yes! > If I use my genuine email address I can then log in. > Thank you for looking into this. > > This is not a change that helps me but I can probably work around it. > Please see https://redmine.postgresql.org/issues/6550#note-27 - whilst I haven't yet tested it myself, it seems you can disable the new behaviour. > > Regards, > Jim Bacon. > > ------------------------------ > *From:* Dave Page <[email protected]> > *Sent:* 25 June 2021 11:17 > *To:* Jim Bacon <[email protected]> > *Cc:* [email protected] < > [email protected]> > *Subject:* Re: Cannot login to pgAdmin4 Web > > Hi > > On Fri, Jun 25, 2021 at 10:41 AM Jim Bacon <[email protected]> > wrote: > > I have a similar problem using the Docker image. With a docker compose > containing > > pgadmin: > # See https://hub.docker.com/r/dpage/pgadmin4/tags > # for other versions available. > image: dpage/pgadmin4:5.3 > environment: > PGADMIN_DEFAULT_EMAIL: [email protected] > PGADMIN_DEFAULT_PASSWORD: password > > I can log in successfully. The moment I change to the 5.4 image, with no > other alteration, I am unable to log in. > > > Does it work if you use a real, deliverable email address? > > We think the problem might be that the flask-security-too module that we > use is now checking to ensure that the address given is actually > deliverable. > > -- > Dave Page > Blog: https://pgsnake.blogspot.com > Twitter: @pgsnake > > EDB: https://www.enterprisedb.com > > -- Dave Page Blog: https://pgsnake.blogspot.com Twitter: @pgsnake EDB: https://www.enterprisedb.com
