Re: cookie based login process

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 60431
interpreted = N
texte = On 12/10/04 4:16 PM, "eLists" wrote: > I am probably over analyzing what I am trying to do, so... if anyone > has any suggestions, gotcha's etc I would certainly appreciate your > input. > > I want to add a cookie based login to one of my sites - using WebDNA > 6.0 on Linux. Just want it to be pretty simple (I think). I expect to > use session cookies with the end user option to allow for a 'remember > me' function. In the case of a remember me function that any of you > might be doing already, do you simply log the user back in (or never > log them out) or do you still present them with a login prompt but > with their username and password already entered? I never log them out, but I give them the option to manually log out. > User enters their username and password, I verify this and set some > cookies based on their existing profile information. > > Now, from page to page, I just check the data in the cookies and hide > the login boxes based on them being 'logged in' > > That seems to be about it I think. Now the tough part, what kind of > data do any of you store in cookies, balancing privacy concerns with > having enough usable data in said cookies to not have to do a ton of > additional searches on each page? I usually store a Customer ID that corresponds to a record in the database. That way, you're not keeping anything in the cookie that private. Then, you can do a [search] or [lookup] to find anything you need to know. > In this case we do not store any sort of financial data on the site at > all. I do want to keep their name, their member ID and probably > location (to be used for certain matching and eventually banner ad > targetting). > > Do end users get uncomfortable when things like their city, state, > country are stored in a cookie? Some end users will get uncomfortable if you store ANYTHING. The best bet is to outline everything in your privacy policy so they know what they're getting into when the submit info on your site. ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: cookie based login process ( "eLists" 2004)
  2. Re: cookie based login process ( Clint Davis 2004)
  3. cookie based login process ( "eLists" 2004)
On 12/10/04 4:16 PM, "eLists" wrote: > I am probably over analyzing what I am trying to do, so... if anyone > has any suggestions, gotcha's etc I would certainly appreciate your > input. > > I want to add a cookie based login to one of my sites - using WebDNA > 6.0 on Linux. Just want it to be pretty simple (I think). I expect to > use session cookies with the end user option to allow for a 'remember > me' function. In the case of a remember me function that any of you > might be doing already, do you simply log the user back in (or never > log them out) or do you still present them with a login prompt but > with their username and password already entered? I never log them out, but I give them the option to manually log out. > User enters their username and password, I verify this and set some > cookies based on their existing profile information. > > Now, from page to page, I just check the data in the cookies and hide > the login boxes based on them being 'logged in' > > That seems to be about it I think. Now the tough part, what kind of > data do any of you store in cookies, balancing privacy concerns with > having enough usable data in said cookies to not have to do a ton of > additional searches on each page? I usually store a Customer ID that corresponds to a record in the database. That way, you're not keeping anything in the cookie that private. Then, you can do a [search] or [lookup] to find anything you need to know. > In this case we do not store any sort of financial data on the site at > all. I do want to keep their name, their member ID and probably > location (to be used for certain matching and eventually banner ad > targetting). > > Do end users get uncomfortable when things like their city, state, > country are stored in a cookie? Some end users will get uncomfortable if you store ANYTHING. The best bet is to outline everything in your privacy policy so they know what they're getting into when the submit info on your site. ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Clint Davis

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[OT] (2002) UPS Ratings and Services free package: version 2 available (2000) [WebDNA] lists opinion (2009) syntax question, not in online refernce (1997) converted seed value? (1998) rename a file (1997) why won't this TCPConnect/Send work? (2004) Protect (1997) formula??? (2000) The IBC root beer has arrived! (1997) WebCatalog NT beta 18 now available (1997) WebCat b15 Mac plug-in (1997) tiny Linux issue (1999) Re1000001: Setting up shop (1997) [OT] Netscape Browser Window (2001) Questions (1998) Creating a folder with WebCat? (2000) Sorting error (1997) Location of Browser Info.txt file (1997) FW: I'll Know If You Don't Read This (2006)