-
Notifications
You must be signed in to change notification settings - Fork 430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrading to new Key Vault (and MSAL) libraries #1413
Conversation
…ed by default (microsoft#1254) * skip AKV test properly * removed enclave properties string to failed errors as enclave tests could be skipped
…sting has not been run yet.
… and remove try / catch in some test code where it is not required.
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.
I just noticed we might be overlooking a scenario in the code changes:
https://github.com/microsoft/mssql-jdbc/pull/1413/files#diff-0a4455f5ffd8e31e9e1badaa7822375eL4454 (Old/Left line 4454 in SQLServerConnection.java)
MSAL should be able to cover the SqlAuthentication.ActiveDirectoryIntegrated scenario, right? Previously the driver had to rely on a native call (ultimately down to adal.dll) that I believe (hope) can now be accomplished via MSAL. We can then eliminate the underlying native call.
src/main/java/com/microsoft/sqlserver/jdbc/SQLServerColumnEncryptionAzureKeyVaultProvider.java
Outdated
Show resolved
Hide resolved
Added tests and catch exception from getKeyClient
added test for token credential and other cosmetic fixes
add tenantID to pipeline and merged with dev
updated for MSAL
Fixed error msgs
This PR migrates from the previous-generation Azure Key Vault library and ADAL libraries to the more modern Azure Key Vault and MSAL equivalents.