Re: WebCat2 beta 11 - new prefs ...

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 10334
interpreted = N
texte = >>Can you explain how to set the new CommandsAllowed and CommandSecurity >>prefs and what their actual functions are? I have an idea about what they >>might do, but I would rather hear it from you than to make the wrong >>assumptions here ... > >When CommandSecurity is F, WebCatalog works as it always has: anyone can >$Append records to a database if they know how. > >When CommandSecurity is T, WebCatalog first checks to see if you are >logged in as an administrator and if so, allows the command. If you are >not an administrator and the command Append is not in the list of >allowed commands, then it is denied.I assume that CommandSecurity also controls all the other commands too? OR does this one deal only with the Append command?If it controls all commands, then setting CommandSecurity to T effectively eliminates everyone but me from appending, replacing, and deleting even if they enter the username and password that appears in the record they are trying to append, replace, or delete - is this correct?I don't want that on my site, so I think I need to set CommandSecurity to F ...Sincerely, Ken Associated Messages, from the most recent to the oldest:

    
  1. Re: WebCat2 beta 11 - new prefs ... (Grant Hulbert 1997)
  2. Re: WebCat2 beta 11 - new prefs ... (Kenneth Grome 1997)
  3. Re: WebCat2 beta 11 - new prefs ... (Kenneth Grome 1997)
  4. Re: WebCat2 beta 11 - new prefs ... (Grant Hulbert 1997)
  5. WebCat2 beta 11 - new prefs ... (Kenneth Grome 1997)
>>Can you explain how to set the new CommandsAllowed and CommandSecurity >>prefs and what their actual functions are? I have an idea about what they >>might do, but I would rather hear it from you than to make the wrong >>assumptions here ... > >When CommandSecurity is F, WebCatalog works as it always has: anyone can >$Append records to a database if they know how. > >When CommandSecurity is T, WebCatalog first checks to see if you are >logged in as an administrator and if so, allows the command. If you are >not an administrator and the command Append is not in the list of >allowed commands, then it is denied.I assume that CommandSecurity also controls all the other commands too? OR does this one deal only with the Append command?If it controls all commands, then setting CommandSecurity to T effectively eliminates everyone but me from appending, replacing, and deleting even if they enter the username and password that appears in the record they are trying to append, replace, or delete - is this correct?I don't want that on my site, so I think I need to set CommandSecurity to F ...Sincerely, Ken Kenneth Grome

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:

Online reference (1997) Problems getting parameters passed into email. (1997) [WebDNA] Dynamic vertical columns (2008) [OT] PHP?MySQL Help Needed (2003) Re:Emailer setup (1997) Sitebuilder (2004) select multiple 2 more cents (1997) [OT] Search Engine Tips (2003) Part Html part WebDNA (1997) WebCat2b15MacPlugIn - [authenticate] not [protect] (1997) Alpha List for Catagory (1998) Calculating multiple shipping... (1997) Wanted how to (1-2-3) (1999) Multiple catalog databases and showcart (1997) Re:2nd WebCatalog2 Feature Request (1996) Checking Out! (1999) Feature req. (2002) Web Catalog 2 demo (1997) Looking up two prices in database? (1997) [WebDNA] Acceleratin Search / Index Performance in a Formum Service (2013)