Fix jdbc scope validator invalid scope issue #5764
Merged
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 jdbc scope validator is enabled, the scopes are not properly validated due to a fix added with PR[1]. The PR[1] was added with the intention of supporting scopes with case sensitivity. The PR[1] uses environmental variable
preservedCaseSensitive
to determine if case sensitivity is enabled or not. This PR will add a separate config to configure this behavior via deployment.toml file.With this PR, we will not change the default behavior which is preserve case sensitivity false.
Add following config to deployment.toml file to enable/disable case sensitivity for jdbc scope validator
Related Issues
Related PRs