Avin,
I agree, the master password nonsense was poorly implemented. I too wish the developers would rethink it. Until then there is a way to disable it by setting an option in a config file. I can provide more details if you would like (or you could look for other more expansive posts by myself on this topic in the list archives).
pgAdmin4 should save your connection passwords in an internal database (separate from the browser) there's a 'save password' option when you are setting up a connection. If that isn't working, you should submit a bug.
If you want to do away with the need for passwords, you can do that at the postgreSQL level by either setting your database to trust the ip address that you are connecting from (in the pg_hba.conf file), or connecting via another means such as SSL.
I hope that helps,
rik.
I'm curious to know where the need for the master password arose and whether it can be disabled or made optional. I don't believe it is needed for personal PCs, the OS login is enough protection.
Every single day, even after getting rid of the "master password" nonsense (which was a nightmare in itself), pgAdmin keeps asking me, again and again, to enter the password when I try to connect to my servers. This is cleared every single time I clear my browser data, which is an absolute necessity multiple times a day.
I don't want pgAdmin to have anything to do with my browser, and dealing with multiple "profiles" is very impractical and tedious to set up. I don't want them connected whatsoever. Please make a proper GUI that is entirely separate from your "normal browser", allowing it to remember passwords and not constantly forget them because it's attached to your normal browser's data.
The GUI can be an embedded browser and has no need whatsoever for constant security updates because all it does is load pgAdmin 4's code. It doesn't need to be able to do anything else, nor should it be able to. It shouldn't even be apparent to the user that it's a browser at all -- it should just open a GUI window with pgAdmin 4 inside of it -- not rely on my browser environment.
I almost recall that this actually was done in the past. Why you would abandon this idea is inexplicable to me, since "just using the normal browser" causes so many annoying problems.