RE: [Rainbowportal-devel] Feature Application Sub System
Brought to you by:
danijel_kecman,
manudea
From: mark m. <mar...@ho...> - 2003-10-09 12:14:20
|
One of the key new concepts I think you are introducing is to allow the 'group authorization' feature currently in rainbow to apply at a database item (row) level as well as at the module level. It is easy in Rainbow today to limit viewing modules to certain groups of users. That feature is built in to all modules. Providing a row-level security mechanism is more problematic. Today we can uniquely identify each row in most (all?) of the modules by the ModuleID and unique ItemID fields. To restrict access to certain rows you could use these fields and another table(s) and set up a filter in the db access layer. -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of Daniel Elebash Sent: Monday, October 06, 2003 4:15 AM To: 'Mark McFarlane'; rai...@li... Subject: RE: [Rainbowportal-devel] Feature Application Sub System It could be different it might be the same, depending on the applications needs you may need data partitioning, ie All users in Group A or all users associated with Company A can only view records added by Company or Group A The Application would have its own menu system I think your answers would fit the need, I have been reading through various posts and the page template with a plug in authentication module seems like it would work Under Modules we could have Applications When you add a new application you can design a menu for the app using the existing menu designer except this menu is tied only to the application Then you could add modules under this app that are custom for the app or use existing portal modules in the app You design an Admin Module for this app maybe using the new plug-in architecture, maybe we inherit the base admin screen then you could add application specific groups, data partitioning or whatever you app needs In my case most of my apps start at the Company level and have users associated with a Company that can only view that data or have certain permissions based on the default setup for that Company That brings me to another idea is the data partitioning we could include this in all modules Ie if not in Admin group then limit user to view only data for that group or company, this could be added to the modules but turned on or off in the Application setup screen With the new authentication plug-in module we might be able to integrate single sign-on with other applications I am working with a few other people to try and formalize what I am thinking hopefully will have a better description and some ideas on how to do this by the end of the week. Dan -----Original Message----- From: Mark McFarlane [mailto:mar...@ho...] Sent: Thursday, October 02, 2003 5:08 AM To: rai...@li... Subject: RE: [Rainbowportal-devel] Feature Application Sub System Sounds like a good idea. When you say " Its almost similar to the multi portal functionality that we have now but more integrated as a page template or application and not a separate portal." ...exactly how would it be different? a) Is it different because in the application you can use a security metaphor that is totally different than Rainbow's current concept of users and groups? b) Are there any other significant differences? If Rainbow had: 1) support for a "page templates" concept 2) an authorization architecture that could be replaced independently for each sub-portal Could you then build your applications as sub-portals and get close enough to what you need? I'm just trying to dig a little here to see if we can accommodate your needs adequately with a few simple concepts that can also be used different ways for different requirements. I think Manu or someone else has already started working on a plug-in authentication and authorization archtiecture. Mark >From: Daniel Elebash <del...@ed...> >To: 'Mark McFarlane' <mar...@ho...>, Daniel Elebash ><del...@ed...>, rai...@li... >Subject: RE: [Rainbowportal-devel] Feature Application Sub System >Date: Wed, 1 Oct 2003 17:37:22 -0400 > >Mark your suggestions are good and similar to what I was thinking but I >wanted to take it one step further on the security > >1) Each Page template can have its on menu system and security >2)Security system will be template specific each template a can either >(per your suggestion) inherit security or have a security module that >allows you to set page template security which may be different then >default rainbow security. It may include data partition, enable >certain buttons on the application menu per user, application groups >and rights that are maintained within the application security and not >part of rainbow groups and rights > >Rainbow already has alot of this functionality that we should be able >to modify to do some of this > >I like the idea of page templates it sounds like what I was thinking, >when you say predefined we should be able create and change the >definition via the web and save the definition for the page template. > >1) Design Menu structure >2) Design Layout >3) Add module definition(grouping of modules on page) >4) Add template definition(can add existing pages to template or >existing templates to template) > If you have accounting template, maybe you want to reuse or add an >existing page in the site or another page template to this templates menu > >So if you have an Accounting Tab and you click on it, it may open up in >a new window with its own menu structure, pages, modules, security, >that was all defined in Rainbow admin screen. Hopefully reusing some >existing modules like contacts and having some custom modules that are >application specific. But in Rainbow admin all you see in the modules >list is Page Template-Accounting or something like that. > >Its almost similar to the multi portal functionality that we have now >but more integrated as a page template or application and not a >separate portal. > >Thanks for the suggestions. > > > > >-----Original Message----- >From: Mark McFarlane [mailto:mar...@ho...] >Sent: Wednesday, October 01, 2003 4:52 PM >To: del...@ed...; >rai...@li... >Subject: Re: [Rainbowportal-devel] Feature Application Sub System > >I have had two related ideas that may meet your needs (but no >implementation > >plans) > >1) I would like to have the concept of 'page templates' supported. A >page template is a pre-defined set of mdoules and their layout on a >page. When you instantiate the template you create a new Page (tab) >with a bunch of predefined modules. > >I can see many applications for this concept. Personally, one of the >groups > >I manage supports about 110 commercial applications, I'd like to have >an identical page for each supported application with events, >announcments, html, some discusions, a fAQ, ... Biulding 100 pages >with 6 or 8 modules is > >a pain. > >2) I'd like to see an inheritance option for security settings. e.g., >set the security for a page and have the option for all existing >modules to get these settings, and all new modules to base their >initial settings on the page. There is some thought that needs to go >into this, but even a basic feature even to push a page's current >security to its modules would be a big help. > >Combining 1 and 2 above may be close to what you are requesting? > >Mark > > > >From: Daniel Elebash <del...@ed...> > >To: "'rai...@li...'" > ><rai...@li...> > >Subject: [Rainbowportal-devel] Feature Application Sub System > >Date: Tue, 30 Sep 2003 16:47:57 -0400 > > > >What do you think about adding in the admin section a way to group >modules > >into a sub application. Example would be to have a tab called > >Accounting System, instead of adding individual modules to the page > >you make a sub system that includes a core set of modules and the sub > >system to rainbow admin screen > > > > > > > >Once you add the sub system a link on the admin page under a user or >group > >lists all sub systems available where you can grant access to, in >addition > >each sub system may have an additional user setup screen that allows > >you >to > >set user specific permissions within that application > > > > > > > >In this way the rainbow portal is not only a base for CMS but also > >web applications like CRM,Accounting, ect > > > > > > > >Haven't thought of the details just wanted to get feedback to see if >anyone > >thinks this is a good idea. > > > > > > > >Thanks. > > > >_________________________________________________________________ >Instant message during games with MSN Messenger 6.0. Download it now >FREE! http://msnmessenger-download.com > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf _______________________________________________ >Rainbowportal-devel mailing list >Rai...@li... >https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel _________________________________________________________________ Instant message during games with MSN Messenger 6.0. Download it now FREE! http://msnmessenger-download.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |