You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c16bf36
Browse filesBrowse the repository at this point in the historyBrowse files
Isolate enclave session cache entries by attestation protocol (#4829)
* Isolate enclave session cache entries by attestation protocol
Include the connection's attestation protocol in the enclave session cache key so a session established under one attestation policy cannot be reused by a connection configured for a different policy. The key is now a tuple, which also keeps server, database and attestation URL as separate fields.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Add end-to-end test for enclave session isolation across attestation protocols
Verifies against a VBS enclave server that sessions created with Attestation Protocol=None and HGS for the same server, database and attestation URL are not shared, for sync and async paths and both connection orders.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Derive None connection string from HGS string in enclave isolation test
The None connection now differs from the HGS connection only by attestation protocol, so the test isolates the cache-key dimension under test.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
(cherry picked from commit f6ae2ac)
// @TODO: Isn't this doing things asynchronously? We should just have a purely asynchronous and a purely synchronous pathway instead of this mix of check this check that and flags.
0 commit comments