camunda / issues

4 stars 0 forks source link

Make Web Modeler work on non-public database schema #874

Open engineering-issue-sync-app[bot] opened 2 months ago

engineering-issue-sync-app[bot] commented 2 months ago

Describe the problem that you are trying to solve

At the moment, Web Modeler contains a problematic Flyway migration V20220209__create_initial_schema.sql which has installing the citext Postgres extension to the public database schema hard-coded:

https://github.com/camunda/web-modeler/blob/b9e7a08549098111cc413cf5e24b900c488330fc/restapi/common/src/main/resources/db/migration/V20220209__create_initial_schema.sql#L3

This is a problem for customers with elevated security requirements where it is not allowed to perform actions on the public schema. Web Modeler has to work on a custom database schema.

Describe the solution you'd like to see implemented

Web Modeler doesn't access a database's public schema.

Describe alternatives you've considered

There is a manual workaround (see https://github.com/camunda/web-modeler/issues/7289) for this which requires one-time access to the public schema. This is not a viable solution for more complex setups.

Additional Context

This solution will implicitly fix errors reported by Flyway when installing to a non-empty database schema, see https://docs.camunda.io/docs/self-managed/modeler/web-modeler/troubleshooting/troubleshoot-database-connection/#using-a-non-empty-schema.

Requested by multiple customers:

Acceptance Criteria (MoSCoW prioritized)

#

Definition of Ready - Checklist

:robot: This issue is automatically synced from: source

alessandrocavalli commented 3 days ago

https://jira.camunda.com/browse/SUPPORT-24781