Protect Tag and Groups

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 15973
interpreted = N
texte = I studied the multigroupchecker. I get the include setup which will work for what I want and, I will set it up separately as you suggest. But part of the logic is still unclear to me.Part of multigroupchecker code is:[search db=Users.db&groupsword=ww&wogroupsdatarq=[uppercase][groups][/uppercase]&eq userdatarq=[uppercase][username][/uppercase]&eqpassdatarq=[uppercase][passw ord][/uppercase]][/search]You are taking the values from [password] and [username] and making them part of the search criteria, but what about [groups]. Where did the value come from inside [groups]. I must be missing part of the logic. It seems to me this searches for a .. whole word/word or .. match to the value entered in [groups] (plus user and pass), but where does that come from?If you wanted to protect an ADMIN page say... wouldn't you change [groups] to ADMIN and let the search function look to see if you wholeword/wordor match the string ADMIN as in ...groupsword=ww&wogroupsdatarq=ADMIN... This code in the include will limit the page to those in the ADMIN group ... right?? How would I use this same kind of search to look for and list all the groups to which a particular user is admitted? When you edit the groups someone is a part of they need only be separated by a space... correct? This shows them listed in whatever groups are listed each separated by spaces. ADMIN Group2 Group3. ------ Original Message ------>A good course of action for what you are describing is to leave the >[protect] tag and Multigroupchecker alone and write your own verification >system. The [protect ] tag is just shorthand for the following: >[include file=multigroupchecker&groups=]. So, create a webdna >[include] file that accesses your database and checks whatever information >you require. If you need to throw up the authenticate dialog, use the >[authenticate] tag. Look at the contents of the multigroup checker for a >good starting point. > >John. > >>I found a reference to this kind of problem in the archive for the list. >>... and it seems a solution. >> >> >> John Hill (johnh@smithmicro.com >> >>To add to my last email, just change the multigroup checker to look at >>your >>new user database file, if youd like, and you can still use the [protect] >>tag! >> >>John. >> >> >>Is it only possible to define groups which the [protect] tag will work >>with other than those in the Users.db. It seems to me the cgi is >>programed only to recognize that particular database. I would like to >>create another separate database if I can for use with this tag. Is that >>possible. If so how? >> >>RH Prouty >>bristol@interpage.net > > > John A. Hill, V.P. Marketing > Pacific Coast Software >eCommerce / Web Developer Tools > http://www.smithmicro.com > > > > Associated Messages, from the most recent to the oldest:

    
  1. Protect Tag and Groups (RH Prouty 1998)
  2. Re: Protect Tag and Groups (Grant Hulbert 1998)
  3. Re: Protect Tag and Groups (Kenneth Grome 1998)
  4. Protect Tag and Groups (RH Prouty 1998)
  5. Re: Fwd: Protect Tag and Groups (John Hill 1998)
  6. Fwd: Protect Tag and Groups (RH Prouty 1998)
I studied the multigroupchecker. I get the include setup which will work for what I want and, I will set it up separately as you suggest. But part of the logic is still unclear to me.Part of multigroupchecker code is:[search db=Users.db&groupsword=ww&wogroupsdatarq=[uppercase][groups][/uppercase]&eq userdatarq=[uppercase][username][/uppercase]&eqpassdatarq=[uppercase][passw ord][/uppercase]][/search]You are taking the values from [password] and [username] and making them part of the search criteria, but what about [groups]. Where did the value come from inside [groups]. I must be missing part of the logic. It seems to me this searches for a .. whole word/word or .. match to the value entered in [groups] (plus user and pass), but where does that come from?If you wanted to protect an ADMIN page say... wouldn't you change [groups] to ADMIN and let the search function look to see if you wholeword/wordor match the string ADMIN as in ...groupsword=ww&wogroupsdatarq=ADMIN... This code in the include will limit the page to those in the ADMIN group ... right?? How would I use this same kind of search to look for and list all the groups to which a particular user is admitted? When you edit the groups someone is a part of they need only be separated by a space... correct? This shows them listed in whatever groups are listed each separated by spaces. ADMIN Group2 Group3. ------ Original Message ------>A good course of action for what you are describing is to leave the >[protect] tag and Multigroupchecker alone and write your own verification >system. The [protect ] tag is just shorthand for the following: >[include file=multigroupchecker&groups=]. So, create a webdna >[include] file that accesses your database and checks whatever information >you require. If you need to throw up the authenticate dialog, use the >[authenticate] tag. Look at the contents of the multigroup checker for a >good starting point. > >John. > >>I found a reference to this kind of problem in the archive for the list. >>... and it seems a solution. >> >> >> John Hill (johnh@smithmicro.com >> >>To add to my last email, just change the multigroup checker to look at >>your >>new user database file, if youd like, and you can still use the [protect] >>tag! >> >>John. >> >> >>Is it only possible to define groups which the [protect] tag will work >>with other than those in the Users.db. It seems to me the cgi is >>programed only to recognize that particular database. I would like to >>create another separate database if I can for use with this tag. Is that >>possible. If so how? >> >>RH Prouty >>bristol@interpage.net > > > John A. Hill, V.P. Marketing > Pacific Coast Software >eCommerce / Web Developer Tools > http://www.smithmicro.com > > > > RH Prouty

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:

Documentation Feedback (1997) For those of you not on the WebCatalog Beta... (1997) WebCatalog Plug-in for Webstar. (1997) emailer (1997) OR-searching (2000) A question on sub-categories (1997) hard carriage returns and sendmail (1998) [WebDNA] WebDNA 7 and Deprecated command (2011) Using tags to create a file name (2000) More than one db with the same namn (was: WC2f3) (1997) ShowNext (1997) WebCat2: multiple currency support (1997) Extended [ConvertChars] (1997) Ampersand (1997) BW in a search (2007) Country & Ship-to address & other fields ? (1997) 300% usage - Clint (2007) Make sure I understand this??? (1997) Grep vs WebDNA: square brackets (2002) Status? (2000)