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:

WC2f3 (1997) WebCatlog vs ColdFusion White Paper (2000) Wanted: More Math Functions (or, Can You Solve This?) (1997) A few questions. . . (1997) Reports of ErrorLog.txt not being written in Linux (2000) # fields limited? (1997) Problem with textA (2000) Resolving variables into field names (1998) [WebDNA] MATH shortcut (2014) [WebDNA] WebDNA as cgi app (was WebSite Examples) (2008) [Cart] ... (1997) form data submission gets truncated (1997) Set Header Context (1998) Less than or equal to........ (1997) PCS Frames (1997) Not really WebCat- (1997) vars (2000) [isfile] ? (1997) [WebDNA] BBEdit (2014) Further on formula.db failure to calculate shipCost (1997)