Fix database web UI connect dialog not allowing users to type/select database username#55532
Merged
gabrielcorado merged 1 commit intomasterfrom Jun 9, 2025
Merged
Conversation
greedy52
approved these changes
Jun 6, 2025
Tener
approved these changes
Jun 9, 2025
Contributor
|
@gabrielcorado See the table below for backport results.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When connecting to the PostgreSQL database using WebUI, the database users select on connect dialog was mistakenly disabled due to the auto-provisioning user flag being set:
Example of wrong UI being shown
The issue was that the auto-provisioning flag didn't consider the user role, only the database config. This PR updates this logic, mimicking the
tshbehavior.UI after the fix
changelog: Fixed database connect options dialog displaying wrong database username options.