Skip to content

Commit 00a15e1

Browse files
authored
Update enable-encrypted-connections-to-the-database-engine.md
1 parent a99afe5 commit 00a15e1

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

docs/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -83,15 +83,15 @@ manager: craigg
8383
> [!NOTE]
8484
> To ensure secure connectivity between client and server, configure the client to request encrypted connections. More details are explained [later in this article](#client-request-encrypt-connect-23h).
8585
86-
87-
8886
### Wildcard Certificates
8987
Beginning with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 2008, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Native Client support wildcard certificates. Other clients might not support wildcard certificates. For more information, see the client documentation. Wildcard certificate cannot be selected by using the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager. To use a wildcard certificate, you must edit the `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQLServer\SuperSocketNetLib` registry key, and enter the thumbprint of the certificate, without spaces, to the **Certificate** value.
88+
9089
> [!WARNING]
9190
> [!INCLUDE[ssnoteregistry_md](../../includes/ssnoteregistry-md.md)]
9291
9392
<a name="client-request-encrypt-connect-23h"/>
94-
## <a name="ConfigureClientConnections"></a> To configure the client to request encrypted connections
93+
94+
## <a name="ConfigureClientConnections"></a> To configure the client to request encrypted connections
9595

9696
1. Copy either the original certificate or the exported certificate file to the client computer.
9797

@@ -101,7 +101,7 @@ Beginning with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 2008, [
101101

102102
4. On the **Flags** page, in the **Force protocol encryption** box, click **Yes**.
103103

104-
## <a name="EncryptConnection"></a> To encrypt a connection from SQL Server Management Studio
104+
## <a name="EncryptConnection"></a> To encrypt a connection from SQL Server Management Studio
105105

106106
1. On the Object Explorer toolbar, click **Connect**, and then click **Database Engine**.
107107

0 commit comments

Comments
 (0)