Creating a SQL Server user authentication schema |
 |
EXPERT RESPONSE FROM: Steven Andres
|
|
|
|
| > |
QUESTION POSED ON: 31 December 2007
How can I generate a SQL Server user authentication/authorization schema (tables/keys/indexes) to support the following requirements:
- A user is required to have a login name, first name, last name, and password.
- A user password will expire in 90 days.
- A user account will be locked after five failed attempts in five minutes.
- A locked account will automatically be unlocked 20 minutes after last failed login attempt.
- A user can change their password but it cannot be the same as any of the last 10 passwords used.
- All data changes have to be tracked and attributable to the person making the changes.
|
|
|
To continue reading for free, register below or login
To read more you must become a member of SearchSQLServer.com
If you are using SQL Server authentication, you will have to put source code in your application to account for "1" and "2". Since SQL Server will be doing the authentication, you won't be able to perform "3" through "6". If you choose to use Windows authentication – more secure with some tradeoffs – you'll be able to set the password complexity and lockout options with a Group Policy Object or Local Security Policy.
|
|
|
|
|
|
|
|
Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
|
|
|
|
|
|
|
|
|
|
|
|
