Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 8ea3646

Browse files
committed
edits
1 parent 68f7ffa commit 8ea3646

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/connect/odbc/connection-troubleshooting.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ ms.topic: conceptual
1111
# Connection Encryption Troubleshooting
1212

1313
### SSL Provider: The certificate chain was issued by an authority that is not trusted.
14-
Connection encryption is now enabled by default in version 18 and newer. Users may see this if the SQL Server is not configured to use certificates. To configure connection encryption for the server, see [Configure SQL Server Database Engine for encrypting connections](../../database-engine/configure-windows/configure-sql-server-encryption.md).
14+
Connection encryption is now enabled by default in version 18 and newer. Users may see this error if the SQL Server isn't configured to use certificates. To configure connection encryption for the server, see [Configure SQL Server Database Engine for encrypting connections](../../database-engine/configure-windows/configure-sql-server-encryption.md).
1515

16-
Users can also choose to set the `Encrypt` connection string keyword to `no`/`optional` to disable connection encryption, which will match the default behavior prior to version 18. In the DSN Configuration UI, this is set using the `Connection Encryption` dropdown. If connection encryption is desired, `TrustServerCertificate` can also be set to `yes` to trust the server's certificate.
16+
Users can also choose to set the `Encrypt` connection string keyword to `no`/`optional` to disable connection encryption, to match the default behavior prior to version 18. In the DSN Configuration UI, this option is set using the `Connection Encryption` dropdown. If connection encryption is desired, `TrustServerCertificate` can also be set to `yes` to trust the server's certificate.
1717

1818
### SSL Provider: The target principal name is incorrect.
19-
Users may see this if the host name in the certificate returned by the server does not match what is expected. By default, the server name is used to check against the certificate. The `HostNameInCertificate` keyword can be used to specify the name expected from the server certificate. Alternatively, a server certificate can also be specified to verify against the returned server certificate by using the `ServerCertificate` keyword (v18.1+). For more information, see [DSN and Connection String Keywords and Attributes](dsn-connection-string-attribute.md).
19+
Users may see this error if the host name in the certificate returned by the server doesn't match what is expected. By default, the server name is used to check against the certificate. The `HostNameInCertificate` keyword can be used to specify the name expected from the server certificate. Alternatively, a server certificate can also be specified to verify against the returned server certificate by using the `ServerCertificate` keyword (v18.1+). For more information, see [DSN and Connection String Keywords and Attributes](dsn-connection-string-attribute.md).
2020

2121
You may also use `TrustServerCertificate` to skip server certificate validation.
2222

0 commit comments

Comments
 (0)