ssl with wildcard certificate

Question

Post reply

ssl with wildcard certificate

Mike Saunders NL

SSChasing Mays

Points: 651
More actions
October 2, 2012 at 4:22 pm

#393292

Hello all,
I have SQL Server 2012 and want to encrypt my connections by using a wildcard (*.domain.com) ssl certificate from a trusted party. After installing my certificate i want to selecti in in de SQL Server Configuration Manager but the certificate does not appear in the properties of protocols.
In older versions it was possible to add the thumprint of my certificate to the registry, but in this version that result into a sql server that cannot be started anymore.
Any people over here who have ideas how to fix this?
Best regards
Mike

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Andrew G SSChampion Points: 12809 More actions · Answer 1

Is the starting problem due to error 26014 ?

If so, read this:

http://nickstips.wordpress.com/2010/09/08/sql-ssl-and-sql-server-2008-service-doesnt-start-error-code-2146885628/

Mike Saunders NL SSChasing Mays Points: 651 More actions · Answer 2

No unfortunaltly i recieve error code 17182 TDSSNICLient initialization failed with error 0xd, status code 0x38.

Reason: an error occured while obtaining or using the certificate for SSL. Check settings in configuration Manager. The data is invalid.

Andrew G SSChampion Points: 12809 More actions · Answer 3

You probably wont have much luck unless someone else has used wildcard certificates on 2012.

Try resolving the error, this thread has a solution (for SQL2005) at the very end:

http://social.msdn.microsoft.com/forums/en-US/sqldatabaseengine/thread/cd738c81-578f-457d-a521-93f34026ece8

It might be something similar

Mike Saunders NL SSChasing Mays Points: 651 More actions · Answer 4

I dont think the problem is wildcard certificate related.

I also tried to use a self signed certificate, but this also not works...

same errors

Mike

arashmasr SSC Journeyman Points: 77 More actions · Answer 5

Hi,

If you did not put your FQDN in the CN field this is the problem.

So can be solved easily.

But when we use a wildcard certificate we have to put something

like *.mydomain.com in the CN field of the certificate,And when we do it the certificate can not be displayed in the Certificate DropDown of the Protocols for MSSQLSERVER Properties.

This is the problem I have 🙁

g.woloszyn SSC Rookie Points: 33 More actions · Answer 6

Hello,

have you maybe solved your problem with wildcard certyficate visibility in SQL Server Configuration Manager?

Regards

KenpoDBA SSCrazy Eights Points: 9811 More actions · Answer 7

Yeah I'd also like to hear if this issue has been resolved.

Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARant

Minion Maintenance is FREE:

jmail 73038 SSC Rookie Points: 40 More actions · Answer 8

The only way to utilize a wildcard certificate on a SQL Server 2012 installation is to manually edit the registry.

Open up the follow key in regedit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer\SuperSocketNetLib.
* Note, if you are setting the certificate for a named instance of SQL Server, adjust the yellow portion of registry path, listed above, to match your SQL Server Instance Name.

Look for the "Certificate" value within this key. If it does not exist, right click the right pane, select New -> String. Set the name to "Certificate". Select "Certificate", right click and choose Modify. Paste in the SHA1 hash for your wildcard certificate, with no colons, no spaces.

Now, look for value named "ForceEncryption". If it doesn't exist, create it as a new DWORD. Set the value to "1".

Now, restart your SQL Server instance and you should be good to go.