You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CREATE ROLE "generic-role";
ALTER ROLE "generic-role" NOLOGIN;
GRANT ALL PRIVILEGES ON DATABASE database TO "generic-role";
Vault creation statement:
CREATE ROLE \"{{name}}\" WITH LOGIN PASSWORD '{{password}}' VALID UNTIL '{{expiration}}' NOCREATEDB NOCREATEROLE NOSUPERUSER;
GRANT generic-role to \"{{name}}\";
With this it will work better.
The text was updated successfully, but these errors were encountered:
Thanks for highlighting this. Maybe a good start could be to update the PostgreSQL secrets engine docs to highlight the limitation and provide the workaround?
Hi @kalafut, I'm not DBA so I don't know if my solution is the best.. This is the workaround I have used. If anyone who knows more about this can confirm the solution, it will be perfect :)
I have had errors in postgresql when lots of roles are created. The error:
This is because the limitation of granting permissions to a role. The best way to do this is not to gran all permissions to the dynamic role. I better to create a "generic" role and then grant the "generic" role to created role:
https://stackoverflow.com/questions/57087519/row-is-too-big-maximum-size-8160-when-running-grant-connect-on-database
Steps:
Create generic role:
Vault creation statement:
With this it will work better.
The text was updated successfully, but these errors were encountered: