Say you have a SQL Server with a "Linked Server" to another server - said "Linked Server" is set to use "Be made using the login's current security context" as its authentication model.
How does the SQL Server provide the correct password (when dealing with non-windows credentials) to the other server when all the server has is a Hash.
I have transferred logins from server to server before and i know that the hash alone is stored in SQL and this is often presented as a hex value hex when creating logins with passwords, for example:
create login test with password = '0x22A9AE652CFC38938D56A9C3872B266B192D16E4' hashed
If SQL only has a hash available - can it logon to the remote server using the hash? Or is the original (un-hashed) password kept in the user’s session / memory for the entire duration of their connection which SQL can then retrieve and pass to the remote server for login?
If the server can login with a hash instead of the password – can this be done in normal logins or is it purely an internal feature of linked servers?
Purely a curiosity question – like to understand how these things work.