Goofy Bullsh!t 2.0 Membership Date Values

  • Thread starter Thread starter clintonG
  • Start date Start date
C

clintonG

What's with this software? Every day its a new surprise with some goofy
bullsh!t.
I finally make time to try to finish building out Membership logging and
reporting and today its user data in the SQL Server 2005 aspnet_Membership
table such as LastLockoutDate and FailedPassword with dates for all users
entered as 1/1/1754.

Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
have used one of my three test users to test getting locked out so I could
learn to use the Unlock method and I certainly did not enter that user's
incorrect credentials on 1/1/1754. I have no idea how the other users have
data has been manipulated either.

What the heck is going on here?

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
 
Sql Server's minimum date is 1/1/1753 .. coincidence ??

I think it is explained pretty well here
http://msdn2.microsoft.com/en-us/library/system.web.security.activedirectorymembershipprovider.aspx
in the membership provider documentation

If user is locked out due to too many bad password attempts, the lockout
time attribute is returned.

If user is locked out due to too many bad password answer attempts, the
value stored in the attribute defined by
attributeMapFailedPasswordAnswerLockoutTime is returned.

If user is locked out due to both a bad password and too many bad password
attempts, the most recent date/time value is returned.

If the account is not locked out, return 1/1/1754 for SQL compatibility.


Cheers,

Greg Young
 
Thanks for your reply Greg. That same document was referred to me
by somebody else and here is my cc reply...

I don't use the AD Provider but I do see by the document you refer to that
the explanation of this goofy date sh!t is much more lucid and complete than
in other documents I did and have read [1] but still happen to have missed
the pithy sentence that is supposed to pass for documentation.

So I know your not getting on my case but it is a ridiculous postulation
that suggests we have to read all documentation Microsoft has ever had
written to learn what should have been clearly and completely elucidated
by a competent tech writer in the first place which could have and should
have then been distributed to others writing documentation for other
providers.

The MSDN2 documentation is GFS compared to earlier efforts. It seriously
lacks clarity and completeness AFIC so thanks again for providing a
reference that while still incomplete is better than what I tried to rely
on.

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

[1]
http://msdn2.microsoft.com/en-us/library/system.web.security.membershipuser.lastlockoutdate.aspx
 
clintonG said:
Thanks for your reply Greg. That same document was referred to me
by somebody else and here is my cc reply...

I don't use the AD Provider but I do see by the document you refer to that
the explanation of this goofy date sh!t is much more lucid and complete than
in other documents I did and have read [1] but still happen to have missed
the pithy sentence that is supposed to pass for documentation.
Click to expand...

I don't think it's too bad in [1] as referenced:

<quote>
The default value for the LastLockoutDate property is determined by the
membership provider. For example, when a membership user is created
using the SqlMembershipProvider provider, the LastLockoutDate property
for the user is initially set to 01/01/1754.
</quote>

That's a good enough explanation for me.
 
Back
Top