Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Password policies checked by CHECK_POLICY


Password policies checked by CHECK_POLICY

Author
Message
Dr. Diana Dee
Dr. Diana Dee
Hall of Fame
Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)

Group: General Forum Members
Points: 3169 Visits: 143
Comments posted to this topic are about the item Password policies checked by CHECK_POLICY
Mohit K. Gupta
Mohit K. Gupta
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1058 Visits: 1089
That is interseting .. I didn't expect that answer.

I expected if SQL Server was told not to force password expirey then following will not be checked:
Enforce password history
Minimum password age

Simplying the following:
Minimum password length
Password must meet complexity requirements

But as I said I assumed, so even though the password does not expire. User can still change their password multiple times. So in your experiment you tried to change password, and it didn't let you change password too soon? And it kept the history for previous password? Thanks for the good question Smile. I'll have to remeber that.

---

Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN.
Microsoft FTE - SQL Server PFE

* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. Smooooth


How to ask for help .. Read Best Practices here.
Dr. Diana Dee
Dr. Diana Dee
Hall of Fame
Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)

Group: General Forum Members
Points: 3169 Visits: 143
Yes, I expected only

Complexity, and
Minimum Length

policies to be checked by CHECK_POLICY.

However, in my experiments, with a SQL Server login having only CHECK_POLICY in effect (but not CHECK_EXPIRATION), when minimum age was set, I could not change the password until then, and with History set I could not change the password to the same one for as many as specified by the History.

Try it and let me know if you get different behavior.

):-D
majorbloodnock
majorbloodnock
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1173 Visits: 3062
At the risk of being obvious, your scenario mentions SQL 2005 running on Windows Server 2003, whilst your tests were SQL 2005 running on Vista. Have you subsequently carried out the same tests on Windows Server 2003 to verify you get the same results?

Semper in excretia, sumus solum profundum variat
Dr. Diana Dee
Dr. Diana Dee
Hall of Fame
Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)

Group: General Forum Members
Points: 3169 Visits: 143
If you have Server 2003, perhaps you could run the experiment and report back to us. NT version 5.2 and version 6.0 should behave the same with respect to policies, but you never know.

I have not had Latin since high school. Please translate.

):-D
majorbloodnock
majorbloodnock
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1173 Visits: 3062
Dr. Diana Dee (11/24/2008)
If you have Server 2003, perhaps you could run the experiment and report back to us. NT version 5.2 and version 6.0 should behave the same with respect to policies, but you never know.

I'll see if I can, but not too sure how quickly I'll be able to come up with an answer - time constraints just like most of us....


I have not had Latin since high school. Please translate.

He, he. You're not the first to ask. Literally, it translates to "Always in the manure; it's only the depth that varies" BigGrin

Semper in excretia, sumus solum profundum variat
Dr. Diana Dee
Dr. Diana Dee
Hall of Fame
Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)

Group: General Forum Members
Points: 3169 Visits: 143
That reminds me of what motivational speaker Doug Wead said:

"If you don't have any horses, your barn will be clean."

):-D
craigpessano
craigpessano
SSCertifiable
SSCertifiable (5K reputation)SSCertifiable (5K reputation)SSCertifiable (5K reputation)SSCertifiable (5K reputation)SSCertifiable (5K reputation)SSCertifiable (5K reputation)SSCertifiable (5K reputation)SSCertifiable (5K reputation)

Group: General Forum Members
Points: 5004 Visits: 2276
I tried this out on Windows 2003 to see how it reacts (Windows 2003 SP2; SQL Server 2005 Standard SP2 64-bit).

Using the SSMS GUI, the following commands are issued.

-- Create the login
CREATE LOGIN [xxx] WITH PASSWORD=N'qwerty12!', DEFAULT_DATABASE=[master], CHECK_EXPIRATION=OFF, CHECK_POLICY=ON
--Command(s) completed successfully.

-- Change the password
ALTER LOGIN [xxx] WITH PASSWORD=N'zxcvbn12!'
--Command(s) completed successfully.

-- Change the password back to the original password
ALTER LOGIN [xxx] WITH PASSWORD=N'qwerty12!'
--Command(s) completed successfully.

-- Change to a password that is too short
ALTER LOGIN [xxx] WITH PASSWORD=N'abc'
--Msg 15116, Level 16, State 1, Line 1
--Password validation failed. The password does not meet Windows policy requirements because it is too short.

-- Change to a password that is not complex enough
ALTER LOGIN [xxx] WITH PASSWORD=N'abcdefgh'
--Msg 15118, Level 16, State 1, Line 1
--Password validation failed. The password does not meet Windows policy requirements because it is not complex enough.


From the above, the only two things that are enforced are
(1) Minimum password length
(2) Password must meet complexity requirements


NOTE that the GUI does not specify OLD_PASSWORD.

Now let's try changing the password this time including the OLD_PASSWORD.

-- Change the password to a previously used password, specifying the old password
ALTER LOGIN xxx WITH PASSWORD = 'zxcvbn12!' OLD_PASSWORD = 'qwerty12!'
--Msg 15115, Level 16, State 1, Line 1
--Password validation failed. The password cannot be used at this time.

-- Change the password to a completely new password, specifying the old password
ALTER LOGIN xxx WITH PASSWORD = 'asdfgh12!' OLD_PASSWORD = 'qwerty12!'
--Command(s) completed successfully.


Interestingly, the old password does not seem to be required, but if specified SQL Server appears to check password history.

-- Clean up
DROP LOGIN xxx




Mohit K. Gupta
Mohit K. Gupta
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1058 Visits: 1089
Old Password is required if a user was changing the password. If you were changing the password with SysAdmin account it doesn't care. It allows for force over-write. Just in case user lock out their account and you need to reset the password Smile.

I tried in SQL Server 2005, SP2.

When I set the password using SA, no issues. I logged on to the user and did password set, and I get this message:

Msg 15151, Level 16, State 1, Line 1
Cannot alter the login 'test', because it does not exist or you do not have permission.

Smile.

---

Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN.
Microsoft FTE - SQL Server PFE

* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. Smooooth


How to ask for help .. Read Best Practices here.
Steve Jones
Steve Jones
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: Administrators
Points: 42462 Visits: 18876
Vista should exceed W2K3 in what is support, if I remember correctly. I don't have a W2K3 server to check on at the moment, but I'll try to later.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search