0

I have two instances on a server. sql 2014 (port 1433) and sql 2016 (port 50019) I have a certificate with SHA1 algorithm on a server that is not expired.

enter image description here

**When sql server started I can clearly see that the above certificate was loaded for encryption (see snip).

enter image description here

Seems like this is NOT self generated certificate, as it doesn't say so.**

However, if I check certificates under SQL configuration manager, I don't see it there.

enter image description here

Also, there is no certificates used under Register keys

enter image description here

So, why it's loaded in a database but can't be found under SQL Configuration and Register Editor? Has it been installed correctly?

Improve this question
3
  • Have you verified the thumbprint of the certificate is the one being loaded by SQL Server?
    – Patrick Keisler
    Jan 12, 2022 at 20:37
  • Yes. thumbprint is verified. That is the one. Thank you
    – Serdia
    Jan 12, 2022 at 20:49
  • 1
    The thumbprint should always be in the registry. Maybe read through the following article to make sure you didn't miss anything. learn.microsoft.com/en-us/sql/database-engine/configure-windows/… You can also verify within SQL that encryption is working. SELECT encrypt_option FROM sys.dm_exec_connections WHERE session_id = @@SPID
    – Patrick Keisler
    Jan 12, 2022 at 21:59

1 Answer 1

Reset to default
1

So, why it's loaded in a database but can't be found under SQL Configuration and Register Editor?

By default, SQL Server will check the certificate store for any certificates that match the requirements to be used for SSL. If one is found then it is used in place of a self-seigned certificate which is generated upon startup (if needed).

Since this is done automagically for you, there is no configuration required, though it is best to be explicitly configured if forcing encryption.

There are various reasons it may not show up in the configuration manager for SQL Server. I've spent far too much time debugging these to know that previous to SQL Server 2019, it's a crap shoot at best.

Has it been installed correctly?

It wouldn't be able to be used if it weren't.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.