Re:Row Level Security with PostgreSQL 9.5
by sandGorgon on Wednesday April 20, 2016 @11:40PM
(#11539524)
The problem is that "set role Alice" is tricky to do with many orm. Which is why group roles are not very effective in postgres. There should be some way to set this on the database itself rather than client side.
Thats a problem with the ORMs.
Re:Row Level Security with PostgreSQL 9.5
by elchief on Thursday April 21, 2016 @01:46PM
(#11543983)
I don't find it tricky at all. It's quite easy with JdbcInterceptor in Java.
The LDAP/AD setup is what I'm most looking forward to trying out. Do you know of any examples of where it's being used currently?
Re:Row Level Security with PostgreSQL 9.5
by mjevans on Wednesday April 20, 2016 @07:36PM
(#11538537)
You can actually use GSS authentication if you setup the correct Kerberos tickets and the correct service names so that Windows will try to communicate with the server via the user's tickets if a password isn't specified.
It's kind of a pain that the configuration options for that have to go in to the host-based authentication file and that it just assumes you know this.
You can still use connection pooling.
PostgreSQL is performant with hundreds of thousands of user accounts (though not pgAdmin).
Connect to database as www (same connection string = you can use pooling)After you get your connection from the pool
When you release you connection back to the pool Want per-database users instead of per-cluster users? See the db_user_namespace settingUse LDAP / AD? Sync users/groups/roles to pg: https://github.com/larskanis/pg-ldap-sync