Fw: Application Testing ( Was: RE: Cactus (Was:Re: RunData & Security Changes) )

2002-01-24 Thread David Sean Taylor
;Brekke, Jeff" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, January 24, 2002 11:42 AM Subject: Application Testing ( Was: RE: Cactus (Was:Re: RunData & Security Changes) ) > FYI: I've moved this reply to the turbine-use

Re: Security Changes

2002-01-16 Thread Paul Spencer
row, then the portlet can be moved down by a portlet that is moved to the first row from an adjacent column. > >> >> >> >> One other area the is related, it the ability to have common portlet(s) >> the are maintained in one place for a group of users.

Re: Security Changes

2002-01-15 Thread Santiago Gala
er area the is related, it the ability to have common > portlet(s) the are maintained in one place for a group of users. As > an example corporate E-mail and corporate News should be on all pages > and in the left column. (I am not ask this be addressed now, just be > aware of thi

Re: Security Changes

2002-01-15 Thread Paul Spencer
Only user's with in the store and warehouse groups will have access to this portlet. All other user will be denied. All users will have access with the "default permissions". The the "Default permissions" need to be defined!

Re: Security Changes

2002-01-15 Thread Santiago Gala
Paul Spencer wrote: > Santiago, > Below is an example implementation of security that I would like to > implement. Please confirm this can be implement in the security model. > "Role" also means "Job Function" > > What are the groups? In turbine's model, a group is a set of resources for whic

Re: Security Changes

2002-01-15 Thread Santiago Gala
David Sean Taylor wrote: >>I propose that each Jetspeed request carries a /group/XXX part. If this >>part is missing, we assume that we are speaking about Turbine's "global" >>group, which (and whose name) cannot be configured without patching >>Turbine. or writing a new security service. This im

Re: Security Changes

2002-01-15 Thread David Sean Taylor
> > I propose that each Jetspeed request carries a /group/XXX part. If this > part is missing, we assume that we are speaking about Turbine's "global" > group, which (and whose name) cannot be configured without patching > Turbine. or writing a new security service. This implies changes in > Defau

Re: Security Changes

2002-01-14 Thread Paul Spencer
Santiago, Below is an example implementation of security that I would like to implement. Please confirm this can be implement in the security model. "Role" also means "Job Function" What are the groups? What are the Roles? What would the directory structure look like? Can you show a sample for

Security Changes

2002-01-14 Thread Santiago Gala
I'm working on a reasonable security implementation, and I see more changes that I anticipated. I wanted to request feed back to see if you agree that I commit. Jetspeed security model is lacking, specially with regards to group/roles. Turbine security model implies that all security checks *