Re: WebCat editing, SiteGuard & SiteEdit
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 10832
interpreted = N
texte = Hi Grant,You said >3) SiteGuard provides the exact same Group abilities that WebCatalog has.you are right, big surprise :-)My mistake, it was SiteEdit I meant doesn't seem to support groups.You also said >1) It doesn't hurt to have remote people send $Quit commands to >WebCatalog. It just reloads databases from disk the next time it needs them.Which we accept and fully agree with.What we specifically want to do is give the WebCat and/or SiteEdit authorized users the ability to quit especially the WebCat.acgi, so that they can test database changes/edits. However, we don't want to give them full ADMIN privileges in either SiteEdit or WebCat ... for obvious reasons. We don't care if the Quit ability is through WebCat or SiteEdit, all we care about is minimizing the distribution of ADMIN privileges.As far as I can tell, the only way to get access to the Quit command for running applications is if you are in SiteEdit with ADMIN access. Am I mistaken ?Thanks, -SvenPS On a related issue, we'd also prefer that they not be able to accidentally shut down WebStar, but that's for a later discussion unless there is a quick fix for that too :-)_____________________________________________________________________ Sven U. Grenander BeeHive Technologies, Inc. http://www.bzzzzzz.com - with a WebCam in Pasadena, California _____________________________________________________________________
Associated Messages, from the most recent to the oldest:
Hi Grant,You said >3) SiteGuard provides the exact same Group abilities that WebCatalog has.you are right, big surprise :-)My mistake, it was SiteEdit I meant doesn't seem to support groups.You also said >1) It doesn't hurt to have remote people send $Quit commands to >WebCatalog. It just reloads databases from disk the next time it needs them.Which we accept and fully agree with.What we specifically want to do is give the WebCat and/or SiteEdit authorized users the ability to quit especially the WebCat.acgi, so that they can test database changes/edits. However, we don't want to give them full ADMIN privileges in either SiteEdit or WebCat ... for obvious reasons. We don't care if the Quit ability is through WebCat or SiteEdit, all we care about is minimizing the distribution of ADMIN privileges.As far as I can tell, the only way to get access to the Quit command for running applications is if you are in SiteEdit with ADMIN access. Am I mistaken ?Thanks, -SvenPS On a related issue, we'd also prefer that they not be able to accidentally shut down WebStar, but that's for a later discussion unless there is a quick fix for that too :-)_____________________________________________________________________ Sven U. Grenander BeeHive Technologies, Inc. http://www.bzzzzzz.com - with a WebCam in Pasadena, California _____________________________________________________________________
Sven U. Grenander
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:
PIXO support (1997)
Shhh, very quiet. (2006)
user flush db (2002)
taxTotal (1997)
WebCat2.0 acgi vs plugin (1997)
OK, here goes... (1997)
how to kill webcat ? (2002)
Mac: LModelDirector bug fix (1997)
UPDATE PROBLEM (1997)
WebTen and WebCat (1997)
WebCatalog2 Feature Feedback (1996)
Re:[ShowIf] and empty fields (1997)
Email Formatting (1998)
Re:Version 2.0 and 1.6 simultaneous (1997)
refreshing IE with posted .tmpl (1997)
More news on 5.0 (2003)
Emailer again & again (1997)
F3 crashing server (1997)
[WebDNA] What Happened To Zero? (2017)
Problems with [Applescript] (1997)