When hosting Mendix in a private cloud (or on-premises) you need to provide your own sql database. The included sql server database driver supports multiple authentication mechanisms, but Mendix only allows username + password authentication.
Mendix already allows customizing most of the connection string via the existing DatabaseJdbcUrl runtime setting. However Mendix always adds a username and password to the jdbc connection string, even if you set a custom connection string. This leads to conflicts in settings, which block other authentication methods than SQL Server.
For example, we want to use Azure Managed Identity authentication in the Azure cloud. The sql server driver supports this. If we configure this in the DatabaseJdbcUrl setting, we get an error from the sql server driver: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot use "Authentication=ActiveDirectoryMSI" with "User", "UserName" or "Password" connection string keywords.
The solution would be to allow to leave the username and password settings empty when using the DatabaseJdbcUrl setting.