89de4d7476
## Review A dedicated reviewer checked the rule description successfully for: - [x] logical errors and incorrect information - [x] information gaps and missing content - [x] text style and tone - [x] PR summary and labels follow [the guidelines](https://github.com/SonarSource/rspec/#to-modify-an-existing-rule)
33 lines
1.3 KiB
Plaintext
33 lines
1.3 KiB
Plaintext
==== Windows authentication (integrated security)
|
|
|
|
When the connection string includes the `Integrated Security=true` parameter, it enables Windows authentication (sometimes called integrated security) for the database connection. With integrated security, the user's Windows credentials are used to authenticate and authorize access to the database. It eliminates the need for a separate username and password for the database connection. Integrated security simplifies authentication and leverages the existing Windows authentication infrastructure for secure database access in your C# application.
|
|
|
|
It's important to note that when using integrated security, the user running the application must have the necessary permissions to access the database. Ensure that the user account running the application has the appropriate privileges and is granted access to the database.
|
|
|
|
|
|
The syntax employed in connection strings varies by provider:
|
|
|
|
[cols="1,1"]
|
|
|===
|
|
|Syntax
|
|
|Supported by
|
|
|
|
|`Integrated Security=true;`
|
|
|SQL Server, Oracle, Postgres
|
|
|
|
|`Integrated Security=SSPI;`
|
|
|SQL Server, OLE DB
|
|
|
|
|`Integrated Security=yes;`
|
|
|MySQL
|
|
|
|
|`Trusted_Connection=true;`
|
|
|SQL Server
|
|
|
|
|`Trusted_Connection=yes;`
|
|
|ODBC
|
|
|
|
|===
|
|
|
|
Note: Some providers such as MySQL do not support Windows authentication with .NET Core.
|