Does Windows 2003 Support Multiple Password Policies?

Sep 15, 2006

We have a need to enforce a more stringent password policy for IDs that have elevated privileges or have access to sensitive data.

Can more than one policy be created in Windows Server 2003 (one that expires every 90 days and another policy that expires every 180 days and requires more complexity)? If this is possible, can SQL Server 2005 use these policies and how are SQL authenticated IDs tied to a specific policy?

This question was posted originally in a MSSQL 2005 forum (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=718231&SiteID=1) and it was suggested that I check a Windows forum for planned changes in this area.

Thank you for your assistance.

View 7 Replies

SQL Server 2005 - How To Create Multiple Password Policies For SQL Authenticated IDs?

Sep 12, 2006

We have a need to have separate password policies for different groups of logins. For example: Those IDs that have greater privileges should be rquired to have more complex passwords that expire more frequently than IDs with lesser privileges.

It appears to me that SQL Server pulls the password policy from the default Active Directory domain group. Is there a way to create/utilize multiple policies for SQL Server authenticated IDs?

Thanks for your assistance.

View 4 Replies View Related

SQL 2005 SP2 - Windows 2003 Ent SP1 - Password Does Not Meet The Password Policy DLL

Jun 18, 2007

I am receiving the following error message when attempting to create a new SQL Authenticated login id.

Password validation failed. The password does not meet the requirements of the password filter DLL. (Microsoft SQL Server, Error: 15119)

I have four servers all running SQL Server 2005 SP2 on Windows 2003 Ent. SP1. Of the four servers, only one received the above error message using the same TSQL below.

CREATE LOGIN TEST_LOGIN WITH PASSWORD = 'pvif9dal' MUST_CHANGE, CHECK_EXPIRATION = ON

All four servers are in the same domain, which if I understand correctly, the password policies are therefore inherited at the OS level by the domain. The password being used is within the password policies of the domain.

Any ideas as to a root cause?

View 5 Replies View Related

Windows Server 2003 Password Policy And SQL Server 2005

Jun 12, 2007

I have a complicated question that involves the password policy defined within Windows Server 2003 and how it is used in Microsoft SQL Server 2005. I recently installed windows server 2003 on my development system. I am a person that prefers to develop in the same OS that our application runs in production. After installing 2003, then a Domain administrator added my machine to our corporate domain. Now, I cannot change the local password policy to allow a simple password. I believe this is due to policy inheriting from the domain that the machine belongs to.

This ties back into SQL Server 2005 because installing sql server on a Server 2003 causes SQL Server 2005 to follow the password policies defined at the OS level. This breaks our application in a subtle way in that we create login accounts for new client databases with random password. Because the password is random it sometimes conforms to the policy and sometimes not.

In production environments, the password policies are configured differently. So I need to one of the following options:

-change the group policy/inherited policy on my machine to not inherity from the domain I joined (prefered solution but don't know HOW)

-change SQL Server to not use OS password policy

-change code to use CREATE LOGIN statement with CHECK_POLICY=OFF or change password generation code to use a stronger password. (don't want to do this as the code change is only accomodating non-production environments)

If someone has a better place to post this question, I would sure appreciate it.