From: | Jeff Sacksteder <jsacksteder(at)gmail(dot)com> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Feature Request |
Date: | 2014-01-20 17:28:27 |
Message-ID: | CAOgeiBa7xZd=yqJCbG8EasbJO+jOMWX0+UPuEtwf88v_L5Oq+Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
It's not clear what list is appropriate for feature requests, so I'm
guessing here.
I'd like to be able to create database connections on Windows using the
currently-logged-in user. Since PgAdmin stores connections per-user, that
can be captured at the time the connection is created instead of
dynamically when the server connection is opened.
It could be a simple as a checkbox called 'Use current windows login'. When
checked, it would fill the username field with the text 'user(at)domain', set
password to blank and lock the fields to prevent input. Or perhaps a set of
radio buttons labled 'Postgres Login' and 'Windows Login'.
It's not so much that typing that in is an issue. The two issues are -
1. Knowing that the username needs to be user(at)domain, not user, domain\user
or user(at)domain(dot)local
2. Knowing that the password field should be left blank. The contents of
this field are disregarded if SSPI is in effect and having it available for
input can produce confusion about what sort of auth is being used or in the
case of auth failure, what the root cause is.
Is this something that can be added to the To-Do list?
From | Date | Subject | |
---|---|---|---|
Next Message | Neel Patel | 2014-01-21 05:15:00 | Re: wxWidgets 3.0 support in pgAdmin |
Previous Message | Dave Page | 2014-01-20 16:29:49 | Re: wxWidgets 3.0 support in pgAdmin |