Azure SQL Server caches the connection which leads to reusable old sessions

[paoliniluis]

Describe the bug

A customer reported that they changed the password in their SQL server and that Metabase can still connect with the old password and not accepting the new one, so I had to see it with my own eyes

To Reproduce

1. create a SQL server on Azure (logical, it's sort of the PaaS SQL server that Azure has)\
2. connect Metabase to it
3. change password of the database
4. see that Metabase keeps working with the old password...

SQL Server in the cloud seems to be using some sort of caching on the handshakes and not checking the password, so old sessions can be reused

Expected behavior

We should be able to connect with the new password

Logs

NA

Information about your Metabase installation

v49.x

Severity

P3

Additional context

This is mostly sure a Microsoft security bug, they can't sacrifice security for performance

NOTE: I tested with a different SQL client and it's the same thing

[paoliniluis]

Microsoft is aware of the situation microsoft/mssql-jdbc#2334