Re: [WebDNA] WebDNA and simple password systems
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102152
interpreted = N
texte = Hi NathanYou can set up secure areas by including code like this on every page that needs protection (see below).On every page that needs it, include the below code with the [include] tag. Pass is a value for the 'IncomingGroupRq' variable. See the docs if you don't know how to pass var's value when including.e.g.: (to protect a page that only admin should see)[include file= CustomProtect.inc&IncomingGroupRq=admin]e.g.: (to protect a page that only YOU should see)[include file= CustomProtect.inc&IncomingGroupRq=webmaster](and you can make as many groups as you want in case there is a 3rd or 4th type of people/access you want to set up... then just add more records to that db and change the value for 'IncomingGroupRq'.) The value for [IncomingGroupRq] should be the group of people that you want to have access. E.g. in your MyCustom-access.db you may have 4 records. 3 of them have "admin" as a value for the 'IncomingGroupRq' field. The 4th record has "webmaster" for that value.Here might be the contents of this MyCustom-access.db :-----TheUser
ThePassIncomingGroupRqnathannatespasswebmasterJoeSiteOwnerjoespassadminJoesHelperhelperspassadminnathan natespassadmin-----Here might be the contents of the CustomProtect.inc :--------[showif NotFound=[lookup db=myDirectory/MyCustom- access.db&lookinField=TheUser&value=[URL][username][/ URL]&returnField=anyField¬Found=NotFound]][authenticate 1][/showif][showif [url][password][/url]![url][lookup db=myDirectory/MyCustom- access.db&lookinField=TheUser&value=[URL][username][/ URL]&returnField=ThePass¬Found=NotFound][/url]][authenticate 2][/showif][search db=myDirectory/MyCustom-access.db&eqTheUserdatarq=[URL] [username][/URL]&eqThePassdatarq=[URL][password][/ URL]&eqIncomingGroupRqdatarq=[URL][IncomingGroupRq][/URL]][showif [numFound]=0][authenticate 3][/showif][/search]--------Hope there are no typos, or other mistakes in my haste. Let us know if you get stuck. You can build a whole 'nother kind of system using cookies/sessions.. which will not use the [authenticate] dialog box.. see the list archives from a couple months ago (or so). a post by Bob Minor - his reply to me. But the code I give here is still reliable.HTH-GovindaOn Mar 9, 2009, at 4:10 PM, Nathan wrote:> Hello,>> I very recently started working in WebDNA and I am a complete newbie > to dynamic site> building in general.>> My client wants to implement a password protected area to http://www.kalvanna.com/> but it was never discussed in the original plan for the site. Since > I didn't> need the site to have a fully functioning store, just product lists > I didn't set the site up> as a sandbox or as a WebDNA template store and naturally the server > admin doesn't> want to set up groups for this one site under the master user > database.>> I was hoping someone would know of resources that could help me > figure it out on my own> or point me in the right direction. I have tried looking into the > dev docs but they only seem to> cover the basics of using the [protect] and [authenticate] tags with > the main users database> and I don't have access to it.>> The information won't be critical data and doesn't need to be super > secure. Any help or advice> would be greatly appreciated.>> Nathan Stenabaugh> http://www.kalvanna.com/>> ---------------------------------------------------------> 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> old archives: http://dev.webdna.us/TalkListArchive/
Associated Messages, from the most recent to the oldest:
Hi NathanYou can set up secure areas by including code like this on every page that needs protection (see below).On every page that needs it, include the below code with the [include] tag. Pass is a value for the 'IncomingGroupRq' variable. See the docs if you don't know how to pass var's value when including.e.g.: (to protect a page that only admin should see)[include file= CustomProtect.inc&IncomingGroupRq=admin]e.g.: (to protect a page that only YOU should see)[include file= CustomProtect.inc&IncomingGroupRq=webmaster](and you can make as many groups as you want in case there is a 3rd or 4th type of people/access you want to set up... then just add more records to that db and change the value for 'IncomingGroupRq'.) The value for [IncomingGroupRq] should be the group of people that you want to have access. E.g. in your MyCustom-access.db you may have 4 records. 3 of them have "admin" as a value for the 'IncomingGroupRq' field. The 4th record has "webmaster" for that value.Here might be the contents of this MyCustom-access.db :-----TheUserThePassIncomingGroupRqnathannatespasswebmasterJoeSiteOwnerjoespassadminJoesHelperhelperspassadminnathan natespassadmin-----Here might be the contents of the CustomProtect.inc :--------[showif NotFound=[lookup db=myDirectory/MyCustom- access.db&lookinField=TheUser&value=[url][username][/ URL]&returnField=anyField¬Found=NotFound]][authenticate 1][/showif][showif [url][password][/url]![url][lookup db=myDirectory/MyCustom- access.db&lookinField=TheUser&value=[url][username][/ URL]&returnField=ThePass¬Found=NotFound][/url]][authenticate 2][/showif][search db=myDirectory/MyCustom-access.db&eqTheUserdatarq=[url] [username][/URL]&eqThePassdatarq=[url][password][/ URL]&eqIncomingGroupRqdatarq=[url][IncomingGroupRq][/URL]][showif [numFound]=0][authenticate 3][/showif][/search]--------Hope there are no typos, or other mistakes in my haste. Let us know if you get stuck. You can build a whole 'nother kind of system using cookies/sessions.. which will not use the [authenticate] dialog box.. see the list archives from a couple months ago (or so). a post by Bob Minor - his reply to me. But the code I give here is still reliable.HTH-GovindaOn Mar 9, 2009, at 4:10 PM, Nathan wrote:> Hello,>> I very recently started working in WebDNA and I am a complete newbie > to dynamic site> building in general.>> My client wants to implement a password protected area to http://www.kalvanna.com/> but it was never discussed in the original plan for the site. Since > I didn't> need the site to have a fully functioning store, just product lists > I didn't set the site up> as a sandbox or as a WebDNA template store and naturally the server > admin doesn't> want to set up groups for this one site under the master user > database.>> I was hoping someone would know of resources that could help me > figure it out on my own> or point me in the right direction. I have tried looking into the > dev docs but they only seem to> cover the basics of using the [protect] and [authenticate] tags with > the main users database> and I don't have access to it.>> The information won't be critical data and doesn't need to be super > secure. Any help or advice> would be greatly appreciated.>> Nathan Stenabaugh> http://www.kalvanna.com/>> ---------------------------------------------------------> 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> old archives: http://dev.webdna.us/TalkListArchive/
Govinda
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:
WebCat2b13MacPlugIn - More limits on [include] (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
State Coalition Approves Internet Sales Tax Plan (2002)
Multiple security dbs (1997)
This list needs a digest: rant, rave... (1997)
RE: protect tag on NT (1997)
Garbage display after 100 records (was WebCatalog usage) (1997)
Questions! (2000)
webcat NT with [dos] command (1997)
READFILE command? (1998)
Practice runs ? (1997)
Problem decrypting encrypted data on different machine (2000)
WCf2 and nested tags (1997)
The Form authentication trick (2000)
Swear words (2002)
search context w shownext works! (1997)
Dummy Credit Card Number for debug? (1997)
Date comparison has serious bug ... (1998)
Date sorting (1997)
[WebDNA] Digest from talk@webdna.us (2017)