Allow overriding of Trusted_Connection parameter in connection string #17
Conversation
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
Trusted connection parameter is automatically set to yes which causes authentication failure when a different authentication method is used. e.g. when using managed identities with azure sql and authentication as ActiveDirectoryMsi
|
|
absci
approved these changes
Mar 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
User may want to override the Trusted_Connection parameter which currently is not possible when using ODBC drivers. In authentication methods such as ActiveDirectoryMsi when using azure sql, this can cause an authentication failure when using system managed identities.
This change does not changes the current behavior of the code but just gives an option to override the parameter when required to prevent authentication failures.