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
In our setup we have a dedicated database user for Dependency-Track that owns the database in order to create tables, but is not a superuser in the database cluster.
As long as that setup is not unusual, creating the uuid-ossp extension in the migration script is a problem since it requires superuser privileges. If run as a superuser the extension can be created, but all tables created by the migration belong to the superuser breaking the application due to missing permissions on these new objects. If run as the regular user, the extension cannot be created and the migration fails.
As a workaround one can create the extension as a superuser before running the script.
The text was updated successfully, but these errors were encountered:
In our setup we have a dedicated database user for Dependency-Track that owns the database in order to create tables, but is not a superuser in the database cluster.
As long as that setup is not unusual, creating the uuid-ossp extension in the migration script is a problem since it requires superuser privileges. If run as a superuser the extension can be created, but all tables created by the migration belong to the superuser breaking the application due to missing permissions on these new objects. If run as the regular user, the extension cannot be created and the migration fails.
As a workaround one can create the extension as a superuser before running the script.
The text was updated successfully, but these errors were encountered: