Jeff, I can't see the need to change the PSML structure. A user should see whatever is defined in his/her PSML file. Really, the control mechanism should be in place at the customization level. That is, a user who is not authorized to see certain content should not have the option of choosing that portlet for viewing in his/her page. Therefore, I would place the the authorization at content (--> jetspeed-config.jcfg or similar) rather than the layout. What do you think?` Thomas ----- Original Message ----- From: "Brekke, Jeff" <[EMAIL PROTECTED]> To: "'JetSpeed'" <[EMAIL PROTECTED]> Sent: Thursday, October 19, 2000 14:20 Subject: RE: ACL's > The proposal hasn't been implemented yet. Changes to PSML must take place. > Currently there is no way to control portlet display at the layout level. > If you are writing your own portlets, you could check the users name or > group in the portlet itself and choose to display the content or a message > or something. > > > -----Original Message----- > > From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, October 19, 2000 6:34 AM > > To: JetSpeed > > Subject: Re: ACL's > > > > > > Is there anyway around to do that ???? with Turbine ACL's ??? > > > > ----- Original Message ----- > > From: "Brekke, Jeff" <[EMAIL PROTECTED]> > > To: "'JetSpeed'" <[EMAIL PROTECTED]> > > Sent: Thursday, October 19, 2000 1:21 PM > > Subject: RE: ACL's > > > > > > > There is a proposal for this in the cvs tree. > > > > > > > -----Original Message----- > > > > From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] > > > > Sent: Thursday, October 19, 2000 4:46 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: ACL's > > > > > > > > > > > > ACL's in Jetspeed : > > > > > > > > I just tried to control the portlet through Jetspeed > > (like show / hide > > > > particular portlet in the portal) based on the ACL stuff. > > > > But I got failed > > > > because of the following strategies. If I am wrong in > > doings, please > > > > correct me and help me to resolve this issue.(atleast > > controlling one > > > > portlet) using ACL. > > > > > > > > As Mr. Kevin Burton is pointing out that Jetspeed can access > > > > and use ACL's > > > > which is in Turbine to control Jetspeed portal. But, as of my > > > > knowledge, the > > > > ACL's which we are using in Turbine is not sufficient for > > > > controlling our > > > > portlet. Turbine ACL's just control entire screen/portal not > > > > our individual > > > > portlet. It is not possibe to control access to a portlet or > > > > part of it > > > > through Turbine. If we have ACL's in jetspeed we can control > > > > our each and > > > > every portlet with in the screen/portal. > > > > > > > > For example, if we want to use Jetspeed in an intranet stuff > > > > like, think > > > > about a portlet which can show the salary of each employee. > > > > In this case we > > > > must have the ability to restrict the usage to people of the > > > > HR department. > > > > On the other hand it is not necessary to enable this > > > > restriction mechanism > > > > on the user level. In general we would restrict the access to > > > > a group of > > > > users (for example the members of the HR department). These > > > > users will be > > > > members of a specific role. As a result we should enable > > > > access to portlet > > > > functionality depending on their roles. Username may still > > > > need to be used > > > > in the access/denial specfication. Otherwise, how do you deny > > > > access to one > > > > user of the HR group, but allow access to all others? We > > > > cannot control this > > > > through Turbine ACL's. > > > > > > > > So we need seperate ACL's which should be in a position > > to control our > > > > individual portlet within portal/screen. > > > > > > > > With Regards, > > > > > > > > Anbunidhi Mahalingam. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > -------------------------------------------------------------- > > > > Please read the FAQ! <http://java.apache.org/faq/> > > > > To subscribe: [EMAIL PROTECTED] > > > > To unsubscribe: [EMAIL PROTECTED] > > > > Archives and Other: <http://java.apache.org/main/mail.html> > > > > Problems?: [EMAIL PROTECTED] > > > > > > > > > > > > > > > -------------------------------------------------------------- > > --------- > > > > > > This message has been scanned for viruses with Trend > > Micro's Interscan > > VirusWall. > > > > > > > > > -- > > > -------------------------------------------------------------- > > > Please read the FAQ! <http://java.apache.org/faq/> > > > To subscribe: [EMAIL PROTECTED] > > > To unsubscribe: [EMAIL PROTECTED] > > > Archives and Other: <http://java.apache.org/main/mail.html> > > > Problems?: [EMAIL PROTECTED] > > > > > > > > > > > -- > > -------------------------------------------------------------- > > Please read the FAQ! <http://java.apache.org/faq/> > > To subscribe: [EMAIL PROTECTED] > > To unsubscribe: [EMAIL PROTECTED] > > Archives and Other: <http://java.apache.org/main/mail.html> > > Problems?: [EMAIL PROTECTED] > > > > > ----------------------------------------------------------------------- > > This message has been scanned for viruses with Trend Micro's Interscan VirusWall. > > > -- > -------------------------------------------------------------- > Please read the FAQ! <http://java.apache.org/faq/> > To subscribe: [EMAIL PROTECTED] > To unsubscribe: [EMAIL PROTECTED] > Archives and Other: <http://java.apache.org/main/mail.html> > Problems?: [EMAIL PROTECTED] > > -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
