Uh oh!
There was an error while loading. Please reload this page.
[Release/2.0] Fix | Fix Enclave Session Cache Issue with Azure Database - #628
Conversation
Uh oh!
There was an error while loading. Please reload this page.
cheenamalhotra
commented
Jul 6, 2020
cc @Xtrimmer |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…ent/SqlColumnEncryptionEnclaveProvider.NetCoreApp.cs Co-authored-by: Cheena Malhotra <v-chmalh@microsoft.com>
…t/SimulatorEnclaveProvider.cs Extended parameter description Co-authored-by: Cheena Malhotra <v-chmalh@microsoft.com>
…ent/EnclaveDelegate.NetStandard.cs Extended parameter description Co-authored-by: Cheena Malhotra <v-chmalh@microsoft.com>
…ent/EnclaveDelegate.NetCoreApp.cs Updated parameter description Co-authored-by: Cheena Malhotra <v-chmalh@microsoft.com>
…veProvider.xml Updated parameter description Co-authored-by: Cheena Malhotra <v-chmalh@microsoft.com>
…veProvider.xml Updated parameter description Co-authored-by: Cheena Malhotra <v-chmalh@microsoft.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| /// <param name="enclaveType">enclave type</param> | ||
| /// <param name="serverName">server name</param> | ||
| /// <param name="enclaveAttestationUrl">url for attestation endpoint</param> | ||
| /// <param name="database">The database that SqlClient contacts to.</param> |
| /// <param name="enclaveType">enclave type</param> | ||
| /// <param name="serverName">servername</param> | ||
| /// <param name="attestationUrl">attestation url for attestation service endpoint</param> | ||
| /// <param name="database">The database that SqlClient contacts to.</param> |
This PR is to fix the issue when connecting to Azure SQL databases with secure enclaves.
The initial enclave session cache key only contains the enclave attestation URL and the server name. It works well with on-prem SQL Servers if we switch between various databases under the same server. However, this will fail for Azure SQL. Sharing the same enclave session among different databases under the same logic Azure server will cause the Azure attestation to fail.
To fix this issue, the database name is also added to the enclave session cache key.