Skip to content

Clarified encryption to fix issue 5534. #5549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 22, 2018
Merged

Clarified encryption to fix issue 5534. #5549

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/framework/data/adonet/sql/authentication-in-sql-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Authentication in SQL Server"
ms.date: "03/30/2017"
ms.date: "05/22/2018"
ms.assetid: 646ddbf5-dd4e-4285-8e4a-f565f666c5cc
---
# Authentication in SQL Server
Expand All @@ -11,7 +11,7 @@ SQL Server supports two authentication modes, Windows authentication mode and mi
- Mixed mode supports authentication both by Windows and by SQL Server. User name and password pairs are maintained within SQL Server.

> [!IMPORTANT]
> 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.
> 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.

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.

Expand Down