| From: | Benedek László <laci(at)benedekl(dot)tvnetwork(dot)hu> |
|---|---|
| To: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | role support |
| Date: | 2010-07-06 14:36:43 |
| Message-ID: | 4C333F7B.9040603@benedekl.tvnetwork.hu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hello hackers,
I createad a patch to add support for roles in saved server configurations.
After a db connection it will issue a SET Role=<rolename> when a rolename is specified for the connected server.
This allows using pgAdmin's gui to create/alter/delete objects in accordance with a security policy that forbids logging in directly
as superuser, but instead specifies that you should log into an admin account and then SET Role to the superuser.
I also found something which seems to me a small escaping bug, a patch included for this issue also.
Please review them for a possible upstream inclusion.
Thank you:
Benedek Laszlo
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Role-support.patch | text/x-patch | 121.4 KB |
| 0002-db-name-escaping-bugfix.patch | text/x-patch | 837 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgAdmin Trac | 2010-07-06 21:24:56 | [pgAdmin III] #208: Small escaping bug in the database name of a connection |
| Previous Message | Dave Page | 2010-07-06 10:18:08 | 1.12 beta 3 |