During setup, you MUST select an authentication mode for the Database Engine. There are two possible modes: Windows Authentication mode and mixed mode. Windows Authentication mode enables Windows Authentication and disables SQL Server Authentication. Mixed mode enables both Windows Authentication and SQL Server Authentication. Windows Authentication is always available and cannot be disabled.
Note: You MUST have the SQL Authentication method setup for the ManEx application and the SQL needs to have a login name for ManEx. For that reason, the choice is less important. Regardless of the method chosen, the user will still have to authenticate via the ManEx security screen.
Configuring the Authentication Mode
If you select Mixed Mode Authentication during setup, you must provide and then confirm a strong password for the built-in SQL Server system administrator account named sa. The sa account connects by using SQL Server Authentication.
If you select Windows Authentication during setup, Setup creates the sa account for SQL Server Authentication but it is disabled. If you later change to Mixed Mode Authentication and you want to use the sa account, you must enable the account. Any Windows or SQL Server account can be configured as a system administrator. Because the sa account is well known and often targeted by malicious users, do not enable the sa account unless your application requires it. Never set a blank or weak password for the sa account. The link below is an article that will show users how to switch to mixed mode if they accidently set their server to only use Windows authentication. http://www.sql-programmers.com/mixed-mode-authentication.aspx
When a user connects through a Windows user account, SQL Server validates the account name and password using the Windows principal token in the operating system. This means that the user identity is confirmed by Windows. SQL Server does not ask for the password, and does not perform the identity validation. Windows Authentication is the default authentication mode, and is much more secure than SQL Server Authentication. Windows Authentication uses Kerberos security protocol, provides password policy enforcement with regard to complexity validation for strong passwords, provides support for account lockout, and supports password expiration. A connection made using Windows Authentication is sometimes called a trusted connection, because SQL Server trusts the credentials provided by Windows.
When using SQL Server Authentication, logins are created in SQL Server that are not based on Windows user accounts. Both the user name and the password are created by using SQL Server and stored in SQL Server. Users connecting using SQL Server Authentication must provide their credentials (login and password) every time that they connect. When using SQL Server Authentication, you must set strong passwords for all SQL Server accounts.
Disadvantages of SQL Server Authentication
· If a user is a Windows domain user who has a login and password for Windows, he must still provide another (SQL Server) login and password to connect. Keeping track of multiple names and passwords is difficult for many users. Having to provide SQL Server credentials every time that one connects to the database can be annoying.
· SQL Server Authentication cannot use Kerberos security protocol.
· Windows offers additional password policies that are not available for SQL Server logins.
Advantages of SQL Server Authentication
· Allows SQL Server to support older applications and applications provided by third parties that require SQL Server Authentication.
· Allows SQL Server to support environments with mixed operating systems, where all users are not authenticated by a Windows domain.
· Allows users to connect from unknown or untrusted domains. For instance, an application where established customers connect with assigned SQL Server logins to receive the status of their orders.
· Allows SQL Server to support Web-based applications where users create their own identities.
· Allows software developers to distribute their applications by using a complex permission hierarchy based on known, preset SQL Server logins.
| 
