Skip to content

Commit 670226f

Browse files
douglaslMSRon Petrusha
authored andcommitted
Clarified encryption to fix issue 5534. (#5549)
1 parent ae5a5a4 commit 670226f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/framework/data/adonet/sql/authentication-in-sql-server.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Authentication in SQL Server"
3-
ms.date: "03/30/2017"
3+
ms.date: "05/22/2018"
44
ms.assetid: 646ddbf5-dd4e-4285-8e4a-f565f666c5cc
55
---
66
# Authentication in SQL Server
@@ -11,7 +11,7 @@ SQL Server supports two authentication modes, Windows authentication mode and mi
1111
- Mixed mode supports authentication both by Windows and by SQL Server. User name and password pairs are maintained within SQL Server.
1212

1313
> [!IMPORTANT]
14-
> We recommend using Windows authentication wherever possible. Windows authentication uses a series of encrypted messages to authenticate users in SQL Server. When SQL Server logins are used, SQL Server login names and passwords are passed across the network, which makes them less secure.
14+
> We recommend using Windows authentication wherever possible. Windows authentication uses a series of encrypted messages to authenticate users in SQL Server. When SQL Server logins are used, SQL Server login names and encrypted passwords are passed across the network, which makes them less secure.
1515
1616
With Windows authentication, users are already logged onto Windows and do not have to log on separately to SQL Server. The following `SqlConnection.ConnectionString` specifies Windows authentication without requiring the a user name or password.
1717

0 commit comments

Comments
 (0)