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]&equserdatarq=[uppercase][username][/uppercase]&eqpassdatarq=[uppercase][password][/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:
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]&equserdatarq=[uppercase][username][/uppercase]&eqpassdatarq=[uppercase][password][/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:
WebCatalog can't find database (1997)
Credit Card Checksum (1997)
Authenticate and IIS (1997)
[ShowNext] (1997)
PGP encrypted email (1998)
Dealer locator (1998)
WebMerchant - MacAuthorize (1999)
View Source from cache (1997)
[WriteFile] problems (1997)
Date in IF ELSE Comparison (2004)
Trigger time setting (2002)
Next (1997)
ODBC (2000)
Error: this shopping cart has already been submittedm (2004)
Grep issue (2003)
[date format] w/in sendmail (1997)
WebCat2b15MacPlugin - [protect] (1997)
whole word matching (2004)
Site Search Suggestions (2004)
Protect (1997)