Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db?
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113077
interpreted = N
texte = 665 Try [session] (http://www.webdna.us/page.dna?numero=3D1009) It is easy to use, much more secure than a cookie and gives you more = control. - chris > On Oct 20, 2016, at 21:47, dale
wrote: >=20 > Hi all, >=20 > Got the user password issue resolved. Now on to user sessions. >=20 > I looked in the archives and saw conversations between a lot of you = regarding this topic. Ken found some issues with the encoding methods = (other than base64) working properly. Some recommended using a = sessions.db >=20 > With the passage of time and enhancements made to WebDNA since then. I = was wondering what the prevailing thoughts are on maintaining user = sessions.=20 >=20 > I will most likely have a maximum of 20-25 users logged in at once. = For most of their shift they won't be very active. their activities will = pretty much follow the below: >=20 > Login > Display systems that need to be worked on for that shift (from a = pre-defined search) > Enter a key list for the vehicle keys they check out > Open a ticket for the first system being worked on (creates work = ticket to avoid losing any data) > Close the ticket (updates work ticket)=20 >=20 > Repeat until shift is over >=20 > Check keys back in from previous list. >=20 > They may be occasionally searching the knowledge base I wrote in = WebDNA. >=20 > The one other thing, hence creating the work ticket on opening it, is = that some of the techs will switch back and forth between their phones = and tablets. I realize I can't carry the session from one device to = another.=20 >=20 > I will set the session timeout to be 5-6 hours as the single longest = task they might have to do is 3-4 hours long. >=20 > I'm not as concerned as some were in the archive posts about security. = I will encrypt the cookies or at least obfuscate them. I won't store the = username and password in clear text.=20 >=20 >=20 > I'm curious as to what pros and cons you have found with either = method.=20 >=20 > Thank you for your insight. >=20 > Dale >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
665 Try [session] (http://www.webdna.us/page.dna?numero=3D1009) It is easy to use, much more secure than a cookie and gives you more = control. - chris > On Oct 20, 2016, at 21:47, dale wrote: >=20 > Hi all, >=20 > Got the user password issue resolved. Now on to user sessions. >=20 > I looked in the archives and saw conversations between a lot of you = regarding this topic. Ken found some issues with the encoding methods = (other than base64) working properly. Some recommended using a = sessions.db >=20 > With the passage of time and enhancements made to WebDNA since then. I = was wondering what the prevailing thoughts are on maintaining user = sessions.=20 >=20 > I will most likely have a maximum of 20-25 users logged in at once. = For most of their shift they won't be very active. their activities will = pretty much follow the below: >=20 > Login > Display systems that need to be worked on for that shift (from a = pre-defined search) > Enter a key list for the vehicle keys they check out > Open a ticket for the first system being worked on (creates work = ticket to avoid losing any data) > Close the ticket (updates work ticket)=20 >=20 > Repeat until shift is over >=20 > Check keys back in from previous list. >=20 > They may be occasionally searching the knowledge base I wrote in = WebDNA. >=20 > The one other thing, hence creating the work ticket on opening it, is = that some of the techs will switch back and forth between their phones = and tablets. I realize I can't carry the session from one device to = another.=20 >=20 > I will set the session timeout to be 5-6 hours as the single longest = task they might have to do is 3-4 hours long. >=20 > I'm not as concerned as some were in the archive posts about security. = I will encrypt the cookies or at least obfuscate them. I won't store the = username and password in clear text.=20 >=20 >=20 > I'm curious as to what pros and cons you have found with either = method.=20 >=20 > Thank you for your insight. >=20 > Dale >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
christophe.billiottet@webdna.us
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:
New WebDNA Solutions ... (1997)
Sendmail truncation in Eudora Clients (1998)
Bug? (1997)
Two options to consider (2008)
HELP WITH DATES (1997)
Sku numbers (1997)
Shipping [grandtotal] solution (1997)
Error 11 (1996)
Tax Rate (2000)
[Fwd: F3 database munching] (1997)
remotely add + sign (1997)
CopyFile not working? (2000)
taxTotal, too (1997)
FYI: virus alert (1996)
[WebDNA] Dynamic vertical columns (2008)
Hosts who have upgraded to v5.0? (2003)
passing variables - problem (1997)
[WebDNA] Interesting business model (2010)
Interfacing WC with mail server (1998)
Date Formats (1997)