Re: pgAdmin4-9.5 password textbox missing in connection settings

Hi Richard,

As we have a release of v9.6 scheduled for next week and limited time for
major changes, we’ve implemented a minimal fix for now.

The "Password" and "Save Password" fields are now editable only when the
server is disconnected. By default, the password field is read-only and
becomes editable only if "Save Password" is set to true. This is because
changing the password has no effect unless it is saved. If the password is
not 'Saved', the user will be prompted to enter the password again when
attempting to connect.

I understand this isn’t a complete solution, but at least the *Password*
and *Save Password* fields will now be visible on the *Connection* tab for
already registered servers.

On Thu, Jul 10, 2025 at 6:28 PM richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>
wrote:

> Hi again,
>
> I can attest that as of 9.1 the password box was always visible in the
> Connection tab, at least on Windows 10.
>
> Why would someone *ever* want to hide somethihng so basic as the text
> input area for the password?
> When would a password textbox never be needed?
>
> These seems to be rather strange UI/workflow choices. From what little
> I've gathered from this breif exchange, it appears that pgAdmin4 has
> switched to a workflow that:
>
> 1. Displays the Password label and textbox only when you first
> Register a server.
> 2. If the password has been saved, and is still valid, it *hides* both
> the Password text and text box on subsequent displays of the Connection tab.
> 3. If the password becomes invalid, then a separate popup dialog is
> presented to the user, independent of the server settings, prompting the
> user to enter the new password.
>
> {insert gif of Buggs Bunny displaying confused contortions here}
> Huh?
>
> Who thought that this was a good road to travel down, and how can it be
> reverted to a more standard workflow?
>
> In my humble opion, you should *never* diable any of the connection
> settings. Especially none of these
>
> - Host
> - Port
> - Username
> - Password
>
> The user should always be able to see and or change these values.
>
> Here are just a few of very common situations which your current workflow
> makes needlessly complicated:
>
> - You are creating/registering server connections for servers or more
> commonly roles, that don't currently exist.
> - You want to change the saved password in preperation of an imminent
> password change on the server.
> - You want to reuse an existing server connection with a different
> username and password (this one happens quite a bit while testing for me
> personally).
>
> I hope this behavior can be changed/reverted to a some
> standard/common/sensible one in the very near future.
>
> Thanks,
> rik.
>
> On Thu, Jul 10, 2025 at 4:07 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>> Hi
>>
>> On Thu, 10 Jul 2025 at 07:16, Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
>> wrote:
>>
>>> Hi Richard/Dave,
>>>
>>> If the server is already registered, the *Password* textbox will not be
>>> visible—this has been the intended behavior for many years, if I recall
>>> correctly. When you attempt to connect, the system will prompt you for the
>>> password if it hasn’t been saved previously.
>>>
>>
>> That seems odd - we normally try to disable rather than hide controls
>> that are not needed in a particular context; precisely to avoid this kind
>> of confusion.
>>
>>
>>>
>>> On Thu, Jul 10, 2025 at 9:39 AM Aditya Toshniwal <
>>> aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
>>>
>>>> Hi Richard/Dave,
>>>>
>>>> I'm on 9.5 on my Mac and I can see the password textbox
>>>>
>>>> [image: image.png]
>>>>
>>>> On Wed, Jul 9, 2025 at 9:17 PM Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, 9 Jul 2025 at 16:28, richard coleman <
>>>>> rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:
>>>>>
>>>>>> I've recently upgraded to pgAdmin4-9.5 from pgAdmin4-9.1 on Windows
>>>>>> 10.
>>>>>> Apparently the Password textbox in the Connection tab has been
>>>>>> removed.
>>>>>>
>>>>>> Why has this change been made?
>>>>>> How do I get it back?
>>>>>>
>>>>>
>>>>> Both good questions - I see the same issue on macOS.
>>>>>
>>>>> --
>>>>> Dave Page
>>>>> pgAdmin: https://www.pgadmin.org
>>>>> PostgreSQL: https://www.postgresql.org
>>>>> pgEdge: https://www.pgedge.com
>>>>>
>>>>>
>>>>
>>>> --
>>>> Thanks,
>>>> Aditya Toshniwal
>>>> pgAdmin Hacker | Sr. Staff SDE II | *enterprisedb.com*
>>>> <https://www.enterprisedb.com/>
>>>> "Don't Complain about Heat, Plant a TREE"
>>>>
>>>
>>
>> --
>> Dave Page
>> pgAdmin: https://www.pgadmin.org
>> PostgreSQL: https://www.postgresql.org
>> pgEdge: https://www.pgedge.com
>>
>>