Randy, Thank you VERY much for your reply. I will give it a shot(using the PermissionManager) and will let you know if I have any problems.Thanks again for the help..
Thanks and regards Kishore On Mon, 2005-09-05 at 23:05 -0600, Randy Watler wrote: > Kishore, > > After all of that, I failed to answer your question, let me try again: > > I think that using the PermissionManager component is indeed equivalent > to using approach #2, but avoids writing directly to the DB under J2. > Yes, a MUCH better solution. You should still take a peek at the > populate-userinfo-for-default-psml.sql so that you can see how the > PageManager will attempt to use the Permissions you create/manage. And > dont forget to enable them using the spring framework definitions in > assembly/page-manager.xml! > > Randy > > > Randy Watler wrote: > > > Kishore, > > > > It is difficult for me to know which of these directions is most > > applicable to your situation, so here are both: > > > > 1. Add an admin portlet that manipulates SecurityConstraints in the > > Page/Folder PSML and writes the pages back to the PSML directory using > > the PageManager component. See the admin site manager portlets to get > > started. > > > > 2. Enable the security permissions mode for the PageManager component, > > (and disable the PSML based SecurityConstraints), in > > /WEB-INF/assembly/page-manager.xml. Then, write an admin portlet to > > manipulate the SECURITY_PERMISSION and PRINCIPAL_PERMISSION tables in > > the J2 database. There is a DB browser portlet in the Public folder > > that you could use to get started I suppose. Also, see the > > /etc/sql/populate-userinfo-for-default-psml.sql file used to configure > > the security permissions tables. > > > > HTH, > > > > Randy > > > > Kishore Sasidharan wrote: > > > >> Hi Randy, > >> > >> Thanks for a quick reply. Can you provide a brief info on the utilities > >> of Permission Manager. I understand that it is a service like > >> RoleManager or GroupManager. In my application I want to create a > >> portlet for the application admin by which he can control the rights > >> (viz. Edit, View) for the various roles. That is where I thought the > >> permission Manager will be useful. Kindly let me know if you can suggest > >> any other options for such a functionality. > >> > >> Thanks in advance, > >> > >> Kishore > >> > >> > >> On Sat, 2005-09-03 at 08:35 -0600, Randy Watler wrote: > >> > >> > >>> Kishore: > >>> > >>> Page security can be modified by editing the Page and Folder objects > >>> directly in code. See the various APIs defined for the Page and > >>> Folder implementaion in the page-manager component. The tricky part > >>> of this is figuring out where to place your code... I am not sure if > >>> portlets can access their PSML Page, Folder, or Fragment definitions. > >>> > >>> At the moment, security constraints/permissions managed by the > >>> portal at the portlet level are not supported. The intent is that > >>> the portlets themselves enforce their own permissions using the > >>> standard portlet API. > >>> > >>> Randy > >>> > >>> Kishore Sasidharan wrote: > >>> > >>> > >>>> Hi > >>>> > >>>> I want to change the security constraints of a page/portlet > >>>> pragmatically. Can the Permission Manager be helpful. How can I change > >>>> the security constraints pragmatically. > >>>> > >>>> Thanks in advance > >>>> Kishore > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>> For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> > >> This e-mail and any files transmitted with it are for the sole use of > >> the intended recipient(s) and may contain confidential and privileged > >> information. > >> If you are not the intended recipient, please contact the sender by > >> reply e-mail and destroy all copies of the original message. Any > >> unauthorized review, use, disclosure, dissemination, forwarding, > >> printing or copying of this email or any action taken in reliance on > >> this e-mail is strictly prohibited and may be unlawful. > >> > >> Visit us at http://www.cognizant.com > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> > >> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
