March 31, 2003 at 11:56 am
In this weeks "Community Update" newsletter there is a link to "Enhanced sp_password". One of the things it does is check for minimum password requirements. I recently wrote a similar function (also verifies there is at least one lower case character). Let me know if anyone sees any possible issues with this:
set @MsgBoxText = 'Password does not meet minimum requirements! Must be' +char(10) + char(13)
+'at least 6 characters, contain a number, and have mixed case'
if len(@password) < 6 return
if convert(varbinary, @password) = convert(varbinary, upper(@password)) return
if convert(varbinary, @password) = convert(varbinary, lower(@password)) return
if charindex('0', @password) = 0 if charindex('1', @password) = 0 if charindex('2', @password) = 0 if charindex('3', @password) = 0
if charindex('4', @password) = 0 if charindex('5', @password) = 0 if charindex('6', @password) = 0 if charindex('7', @password) = 0
if charindex('8', @password) = 0 if charindex('9', @password) = 0 return
March 31, 2003 at 12:54 pm
I know this is standard boilerplate, but remember that such changes are not supported by Microsoft. Should they encounter an issue when you place a support call, they might ask you to change back the stored procedure if they discover the difference.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply