>>Did you read JS1-480? I will please ignorance and say 'No I did not need read JSI-480, in fact I don't know what a JSI is. I do know JSRs.'
Is there somewhere I can go to learn more? Also, I created an 'Admin and Owner' security constraint and applied it to the new user template. How do I contribute that back?? Thanks Bob -----Original Message----- From: David Sean Taylor [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 12:58 AM To: Jetspeed Users List Subject: Re: What is the default Group Profile? On May 25, 2004, at 3:07 PM, Bob Fleischman wrote: > David: > > I've looked this over. From what I can tell the Security constraint is > inherited from the default new user template. > > Does that sound right to you?? Thats how it currently operates. Did you read JS1-480? Does that proposal better fit your requirements, or is the current implementation fine? > > -----Original Message----- > From: David Sean Taylor [mailto:[EMAIL PROTECTED] > Sent: Monday, May 24, 2004 12:12 PM > To: Jetspeed Users List > Subject: Re: What is the default Group Profile? > > > > On May 21, 2004, at 2:48 PM, Bob Fleischman wrote: > >> And where is it created? >> >> I am familiar with services.Profiler.newuser.template for new users, >> but I >> did not see anything similar for groups. >> >> I would like to intercept the process and customize the Profile/PSML >> that is >> created for each group so that I can quickly create team workspaces. >> >> Has anyone else tried this?? >> > Easy to change the default behavior, see > o.a.j.services.security.turbine.TurbineGroupManagement.addDefaultGroupP > S > ML, and then see the > o.a.j.services.profiler.JetspeedProfilerService.createProfile > You can extend these services, or better yet if we can come up with a > generic solution to your problem, commit it back to CVS head > > I noticed 2 issues that can be improved on: > > 1. The Turbine User (the default User template) was copied over and > used as a default Group template. > 2. The Security constraint applied (owner-only) makes this PSML > unaccessible > > I propose > > 1. enhancing the TurbineGroupManagement : adding a default Group > template > 2. changing the default security constraint to admin-all / owner-only > for user resources, and admin-all + particular role or group for new > group or role resources > This will require creating a new role or group constraint on template > creation > > See JIRA issue: > > http://nagoya.apache.org/jira/browse/JS1-480 > > > --------------------------------------------------------------------- > 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] > > -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 --------------------------------------------------------------------- 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]
