(1)
Is there any way to allow access to a file on a V8 Application Server with Security Framework turned on, where the file has NOT been published from Alpha Five and in fact the project does not yet exist? Situation is where a brand new folder is created under A5Webroot, and a file named welcome.htm will be placed in that new folder - but the project has not been created yet, therefore no security files have been published to this new project location.
I guess I am asking if there is any global override per server by filename, or file extension. Per project you can do this, but not per server as far as I can tell.
If not, then is it possible to create "stock" web_security files that give welcome.htm an Always Allow setting, and copy (not publish) those files along with my welcome.htm file to the new project location, thereby allowing access to welcome.htm, even though the project has not been created or published.
(2)
Given that Security Framework is toggled on or off at the server level, is there any way to toggle SF on or of by project, or by subfolder. So c:\A5Webroot\Site1 will have SF on, and c:\A5Webroot\Site2 will have SF off?
(3)
Is there any inheritance for security? I have found situations where if a file has permissions set in one directory, a file with the same name, in a subfolder will have the same permissions. For example, if c:\W5Webroot\myfile.a5w is set to Always Allow, then c:\A5Webroot\newfolder\myfile.a5w is automatically rendered Always Allow. Its quite possible to create this situation in a web project, but the Web Security / Page Security Assignment does not seem to be able to handle this (because it does not acknowledge subfolders off the project folder).
Is there any way to allow access to a file on a V8 Application Server with Security Framework turned on, where the file has NOT been published from Alpha Five and in fact the project does not yet exist? Situation is where a brand new folder is created under A5Webroot, and a file named welcome.htm will be placed in that new folder - but the project has not been created yet, therefore no security files have been published to this new project location.
I guess I am asking if there is any global override per server by filename, or file extension. Per project you can do this, but not per server as far as I can tell.
If not, then is it possible to create "stock" web_security files that give welcome.htm an Always Allow setting, and copy (not publish) those files along with my welcome.htm file to the new project location, thereby allowing access to welcome.htm, even though the project has not been created or published.
(2)
Given that Security Framework is toggled on or off at the server level, is there any way to toggle SF on or of by project, or by subfolder. So c:\A5Webroot\Site1 will have SF on, and c:\A5Webroot\Site2 will have SF off?
(3)
Is there any inheritance for security? I have found situations where if a file has permissions set in one directory, a file with the same name, in a subfolder will have the same permissions. For example, if c:\W5Webroot\myfile.a5w is set to Always Allow, then c:\A5Webroot\newfolder\myfile.a5w is automatically rendered Always Allow. Its quite possible to create this situation in a web project, but the Web Security / Page Security Assignment does not seem to be able to handle this (because it does not acknowledge subfolders off the project folder).
Comment