-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Fix passing null for credentials in SqlConnectionPoolKey #34260
Conversation
| conn3.Open(); | ||
| conn4.Open(); | ||
|
|
||
| SecureString NewPassword = new SecureString(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: newPassword
|
cc @danmosemsft @afsanehr it would be good to send a PR to master as well and have that merged before the release branch is merged with Shiproom approval. |
|
Please wait for branch to open in about 2-3 weeks. Approx 2/12. |
|
@danmosemsft do we need to port this to other branch or is it considered complete? If so, let me know please so I can close the related issue #34205 Thanks! |
|
Is there a reason this PR was specifically opened in release/2.2? Was there also a PR opened in release/2.1? |
|
I see, that makes sense. I'll make the necessary changes to ensure this gets shipped with 2.2.3. |
|
That one's good to go, Santi already made the necessary packaging changes. |
Fixes #34205
Description
Null is passed for credentials when calling SqlConnectionPoolKey ChangePassword method.
Customer Impact
Wrong connection pool gets cleared when calling ChangePassword using a SecureString.
Regression
No, since this code path exists in .Net Framework and credential is mistakenly passed as null.
Risk
High. A password change may cause the connections from wrong pool to be killed causing unexpected application disruption.