Skip to content
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

Merged
merged 168 commits into from
Oct 14, 2020

Conversation

srnagar
Copy link
Member

@srnagar srnagar commented Aug 25, 2020

This PR migrates from the previous-generation Azure Key Vault library and ADAL libraries to the more modern Azure Key Vault and MSAL equivalents.

lilgreenbird and others added 30 commits February 5, 2020 11:03
…ed by default (microsoft#1254)

* skip AKV test properly

* removed enclave properties string to failed errors as enclave tests could be skipped
… and remove try / catch in some test code where it is not required.
Copy link
Contributor

@David-Engel David-Engel left a 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.

peterbae
peterbae previously approved these changes Oct 10, 2020
build.gradle Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Public API Changes in Public API
Projects
MSSQL JDBC
  
Closed/Merged PRs
Development

Successfully merging this pull request may close these issues.

None yet

7 participants