473,322 Members | 1,401 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,322 software developers and data experts.

Goofy Bullsh!t 2.0 Membership Date Values

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/
Jun 5 '06 #1
3 1554
Sql Server's minimum date is 1/1/1753 .. coincidence ??

I think it is explained pretty well here
http://msdn2.microsoft.com/en-us/lib...pprovider.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
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:OR**************@TK2MSFTNGP02.phx.gbl...
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/

Jun 5 '06 #2
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/lib...ckoutdate.aspx


"Greg Young" <dr*******************@hotmail.com> wrote in message
news:uP**************@TK2MSFTNGP04.phx.gbl...
Sql Server's minimum date is 1/1/1753 .. coincidence ??

I think it is explained pretty well here
http://msdn2.microsoft.com/en-us/lib...pprovider.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
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:OR**************@TK2MSFTNGP02.phx.gbl...
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/


Jun 6 '06 #3
clintonG <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote:
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.


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.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Jun 12 '06 #4

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
by: Blair Fraser | last post by:
This seems incredibly bizzare. I'm trying to sub in a string with a backslash using re.sub. If that string has a \b in it I can't stop it from being interpreted as a backspace, even though the...
4
by: Jozef | last post by:
Hello, I have forms in my database that use grey as the back color. When I convert them to XP, They all look goofy. The grey becomes two tone. The grey used in the controls are dark, the grey...
8
by: Giorgio | last post by:
Hi all, i have a problem with a website where i use asp 3 and a global.asa in the root. In global.asa i use some aaplication variables which contains strings, such as: Application("str1")="text"....
3
by: Andre Ranieri | last post by:
Hello, I would certainly appreciate some feedback to the issue I'm experiencing in my first major WMI application. When I navigate to a new child form I usually dispose of the one I'm...
1
by: Andre Ranieri | last post by:
Hello, I apologize for multiple posting of this question but I used the wrong acronym earlier. I meant to say MDI. I would certainly appreciate some feedback to the issue I'm experiencing in...
66
by: mensanator | last post by:
Probably just me. I've only been using Access and SQL Server for 12 years, so I'm sure my opinions don't count for anything. I was, nevertheless, looking forward to Sqlite3. And now that gmpy...
4
by: Hillbilly | last post by:
Maybe this is or isn't some kind of bug but it sure is goofy and remains a mystery that really has me puzzled for two reasons... // goofy syntax functions as expected... Panel finalStepButton =...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.