Package: django-postgresql-setrole27
django-postgresql-setrole27This is a Python 2.7 port of Jonas Maurus’ django-postgresql-setrole
package.A Django application that executesSET ROLEon every connection to PostgreSQL
opened by Django. This is useful if you’re using external authentication
managers likeHashicorp Vault.PostgreSQL’s user model (“roles”) assigns every object created in a database/
tablespace/schema an “owner”. Said owner is theonlyuser that can modify or
drop the object. This means that user credentials leased from Vault which
expire after some time, can’t be used to create or migrate tables unless you
use the same user name every time (which would defeat the purpose).The solution is to create an “owner role”. In layman’s terms “a group that has
all necessary permissions on the database and the INHERIT attribute and will
act as the ‘sudo’ user for leased users from the authentication manager”. All
users created by the authentication manager will then be assigned this group
and when they connect to the database execute “SET ROLE <owner role>”, thereby
making all objects created owned by the owner role.How do I use this Django application?Addpostgresql_setrole27toINSTALLED_APPS. Then insettings.DATABASESaddDATABASES={"default":{...,# other settings"SET_ROLE":"mydatabaseowner",}}Why is SET ROLE necessary?TheINHERITattribute is not bidirectional. So if a (user) role is assigned
a (group) role it inherits the group’s permissions, but the group does not
gain any rights on objects created by the user role.So what you want is the (group) owner role to own everything.How do I set this up?On your shell as thepostgressuperuser:# --- create an admin role for Vault
# no create database
# encrypt password
# do not inherit rights
# can create roles
# not a superusercreateuser-D-E-I-l-r-Svaultadmin# --- create an owner role for your database
# no create database
# encrypt password
# do not inherit rights
# can't create roles
# not a superusercreateuser-D-E-I-L-R-Smydatabaseownercreatedb-Eutf8-OmydatabaseownermydatabaseThen configure Vault to create roles like this:$vaultmount-path=mydatabase-authpostgresql$vaultwritemydatabase-auth/roles/fullaccess-{"sql":"CREATE ROLE \"{{name}}\" WITH LOGIN ENCRYPTED PASSWORD '{{password}}' VALID UNTIL '{{expiration}}' IN ROLE \"mydatabaseowner\" INHERIT NOCREATEROLE NOCREATEDB NOSUPERUSER NOREPLICATION NOBYPASSRLS;","revocation_sql":"DROP ROLE \"{{name}}\";"}Then users created by Vault when they log in must runSETROLE"mydatabaseowner";This ensures that all created tables and other objects belong tomydatabaseowner.LicenseCopyright (c) 2016, Jonas Maurus
All rights reserved.Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.Neither the name of the copyright holder nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.