Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need to grant permissions to PUBLIC? #178

Open
ePaul opened this issue Aug 15, 2023 · 0 comments
Open

Do we need to grant permissions to PUBLIC? #178

ePaul opened this issue Aug 15, 2023 · 0 comments
Labels
auto-configuration everything about the auto-configuration features persistence everything around DB access

Comments

@ePaul
Copy link
Member

ePaul commented Aug 15, 2023

Current situation
Currently, our DB setup gives permissions on the event_log table to PUBLIC (i.e. every DB user).

The purpose of this is to allow running only the migrations using a higher-privileged user, and have application connect with a lower-privileged one.
But it seems like granting this to public goes a bit further than needed – now even the monitoring robot user can insert into the eventlog table (or, after #177, also delete from there).

Ideal situation

Ideally we would only grant the access to the application user (and maybe to human users with administration privileges).

Implementation notes

The problem here is that the flyway script is static (part of our jar file), and the user name might be different for every application where this is running. We might need flyway placeholders, or java-based migrations for setting this up.

@ePaul ePaul added auto-configuration everything about the auto-configuration features persistence everything around DB access labels Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-configuration everything about the auto-configuration features persistence everything around DB access
Projects
None yet
Development

No branches or pull requests

1 participant