It seems like Slide allows one instance per VM and its security control is all or nothing. What are the options for implementing finer grained security?
One option might be to have root directory (or repository, space, etc.) per portal instance. The Portal instance administrator can assign User Groups that have read or write access to the per instance root directory. This root directory can be assigned by the administrator of the Portal. Since Slide's allows for one root repository, the per-portal instance root can be one of the sub-directories under the Slide root. Example: Let's say that the Slide root points to /var/jbpfiles/ And there is a directory in it named portal2files. Someone creates a new portal instance named portal2. Then assigns portal2files as the root WebDav dir for this portal instance. Users should be now accessing files under portal2 using URLs like http://host/portal2/files/somefile.txt. The portal2 admins can configure which User Groups have read and which user groups have write access to the webdav repository. So FullAccessUsers will have read/write access, meaning that users logged in to portal2 that belong to FullAccessUsers will be able to see and create files under /var/jbpfiles/portal2files. Thoughts? Ivelin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861814#3861814 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861814 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
