For your second problem, it is hard to say what happened based on the information you provided. Anyhow, you can put in some debug statements (using the jetspeed logger) in the PortletWraper class then check the output in the jetspeed.log file. The checkPermission method in there will invoke the AccessController class you choose in the JetspeedSecurity.properties file. Default is the RegistryAccessController. You can put in debug statements in the AccessController class if necessary. These should give you enough information to tell you why your access control doesn't work. Andy
-----Original Message----- From: Sturtz, Andrew [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 30, 2004 3:13 PM To: [EMAIL PROTECTED] Subject: Problems with Roles and Permissions I am trying to divide users into two seperate groups using two different roles and setting permissions for these roles to be able to view certain portlets ie. one group with a role of A can see one set of portlets, while users with the role of B can see another set of portlets. The problem that I am running into is that everytime a change a role of a user I have to restart Tomcat for the changes to take effect. Is this normal behavior? It doesn't seem so, because in a production environment that would be very detrimental to the users already set up, if throughout the day their portal would not be available to them because it is constantly being restarted. A second problem that I am running into is that after I set the roles and add the permissions to my security.xreg file and then add the security reference to the individual portlets, the restricted portlets are still available to the users that are not supposed to be able to see them. Please help!!! :-( Thanks in advance!!!!! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
