You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Armando Arteaga <ka...@gmail.com> on 2006/02/16 18:50:58 UTC

Administration and User Pages

Hi:
  I have a problem with the security-constraints of Jetspeed2. I'm testing
the deploy that comes with the installation package. First of all, i've
looked everywhere in j2-admin portlets and there doesn't seem to exist a
constraint manager per portlet like there was in jetspeed 1.x. Also I think
there's no way to view the user pages with the manager or admin users.  The
folder.metadata in the user folder declares the security constraints as
follow:

<security-constraints>
    <owner>user</owner>
    <security-constraints-ref>manager</security-constraints-ref>
  </security-constraints>

and the page.security of the portal defines the manager ref as:
<security-constraints-def name="manager">
    <security-constraint>
      <roles>manager</roles>
      <permissions>view</permissions>
    </security-constraint>
  </security-constraints-def>

I'm making the assumption that this means the 'admin'/'manager' user (they
have the 'manager' role assigned to them) could at least view the pages
contained here, but when i'm logged in with this users and i try to view
these pages with the link provided by the Portal Site Detail Portlet it just
redirects me to the previous page i was before entering the Administrative
Portlets.  Is this the way it is supposed to work?

PS: Sorry for my horrible english.

Re: Administration and User Pages

Posted by Randy Watler <wa...@wispertel.net>.
Armando,

Please search the archives of this list for tips... there have been
plenty of them over the last year. Also, there are design docs in the
SVN repo that include discussions on this topic. Refer to the Profiler,
Page Manager, and Portal Site components.

HTH,

Randy

On Fri, 2006-02-17 at 10:20 -0500, Armando Arteaga wrote:
> Thanks for the reply.  I don't quite understand about profilers. I tried to
> by reading http://portals.apache.org/jetspeed-2/guides/guide-profiler.html ,
> but it seems the informatioin here isn't complete and i don't understand
> what's already there (lil'pumpkin they call me XD).  Can anyone tell me
> where to find a good example about what does profiling exactly do,
> description of all the posible rules and how to configure it?
> 
> On 2/16/06, David Sean Taylor <da...@bluesunrise.com> wrote:
> >
> > Armando Arteaga wrote:
> > > Hi:
> > >   I have a problem with the security-constraints of Jetspeed2. I'm
> > testing
> > > the deploy that comes with the installation package. First of all, i've
> > > looked everywhere in j2-admin portlets and there doesn't seem to exist a
> > > constraint manager per portlet like there was in jetspeed 1.x. Also I
> > think
> > > there's no way to view the user pages with the manager or admin
> > users.  The
> > > folder.metadata in the user folder declares the security constraints as
> > > follow:
> > >
> > > <security-constraints>
> > >     <owner>user</owner>
> > >     <security-constraints-ref>manager</security-constraints-ref>
> > >   </security-constraints>
> > >
> > > and the page.security of the portal defines the manager ref as:
> > > <security-constraints-def name="manager">
> > >     <security-constraint>
> > >       <roles>manager</roles>
> > >       <permissions>view</permissions>
> > >     </security-constraint>
> > >   </security-constraints-def>
> > >
> > > I'm making the assumption that this means the 'admin'/'manager' user
> > (they
> > > have the 'manager' role assigned to them) could at least view the pages
> > > contained here, but when i'm logged in with this users and i try to view
> > > these pages with the link provided by the Portal Site Detail Portlet it
> > just
> > > redirects me to the previous page i was before entering the
> > Administrative
> > > Portlets.  Is this the way it is supposed to work?
> > >
> > Yes
> >
> > ALSO want to point out that the Portlet Selector will filter out
> > portlets based on the permissions in the Jetspeed Security Policy.
> > Thus you can only add portlets that you have access to.
> > Its been debated whether we should also make this check during
> > rendering, probably she be optional.
> >
> > Im working on an XML version of the permissions for import/export, but
> > for now the only way to edit this policy is to edit the database
> > scripts. For example, this permission secures ALL the j2-admin portlets:
> >
> > INSERT INTO SECURITY_PERMISSION
> > VALUES(100,'org.apache.jetspeed.security.PortletPermission
> > ','j2-admin::*','view,
> > edit','2004-05-22 16:27:12.572','2004-05-22 16:27:12.572');
> > INSERT INTO PRINCIPAL_PERMISSION VALUES(6,100);
> >
> > Future version will support editing of these permissions via the
> > j2-admin portlets
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org


Re: Administration and User Pages

Posted by Armando Arteaga <ka...@gmail.com>.
Thanks for the reply.  I don't quite understand about profilers. I tried to
by reading http://portals.apache.org/jetspeed-2/guides/guide-profiler.html ,
but it seems the informatioin here isn't complete and i don't understand
what's already there (lil'pumpkin they call me XD).  Can anyone tell me
where to find a good example about what does profiling exactly do,
description of all the posible rules and how to configure it?

On 2/16/06, David Sean Taylor <da...@bluesunrise.com> wrote:
>
> Armando Arteaga wrote:
> > Hi:
> >   I have a problem with the security-constraints of Jetspeed2. I'm
> testing
> > the deploy that comes with the installation package. First of all, i've
> > looked everywhere in j2-admin portlets and there doesn't seem to exist a
> > constraint manager per portlet like there was in jetspeed 1.x. Also I
> think
> > there's no way to view the user pages with the manager or admin
> users.  The
> > folder.metadata in the user folder declares the security constraints as
> > follow:
> >
> > <security-constraints>
> >     <owner>user</owner>
> >     <security-constraints-ref>manager</security-constraints-ref>
> >   </security-constraints>
> >
> > and the page.security of the portal defines the manager ref as:
> > <security-constraints-def name="manager">
> >     <security-constraint>
> >       <roles>manager</roles>
> >       <permissions>view</permissions>
> >     </security-constraint>
> >   </security-constraints-def>
> >
> > I'm making the assumption that this means the 'admin'/'manager' user
> (they
> > have the 'manager' role assigned to them) could at least view the pages
> > contained here, but when i'm logged in with this users and i try to view
> > these pages with the link provided by the Portal Site Detail Portlet it
> just
> > redirects me to the previous page i was before entering the
> Administrative
> > Portlets.  Is this the way it is supposed to work?
> >
> Yes
>
> ALSO want to point out that the Portlet Selector will filter out
> portlets based on the permissions in the Jetspeed Security Policy.
> Thus you can only add portlets that you have access to.
> Its been debated whether we should also make this check during
> rendering, probably she be optional.
>
> Im working on an XML version of the permissions for import/export, but
> for now the only way to edit this policy is to edit the database
> scripts. For example, this permission secures ALL the j2-admin portlets:
>
> INSERT INTO SECURITY_PERMISSION
> VALUES(100,'org.apache.jetspeed.security.PortletPermission
> ','j2-admin::*','view,
> edit','2004-05-22 16:27:12.572','2004-05-22 16:27:12.572');
> INSERT INTO PRINCIPAL_PERMISSION VALUES(6,100);
>
> Future version will support editing of these permissions via the
> j2-admin portlets
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>

Re: Administration and User Pages

Posted by David Sean Taylor <da...@bluesunrise.com>.
Armando Arteaga wrote:
> Hi:
>   I have a problem with the security-constraints of Jetspeed2. I'm testing
> the deploy that comes with the installation package. First of all, i've
> looked everywhere in j2-admin portlets and there doesn't seem to exist a
> constraint manager per portlet like there was in jetspeed 1.x. Also I think
> there's no way to view the user pages with the manager or admin users.  The
> folder.metadata in the user folder declares the security constraints as
> follow:
> 
> <security-constraints>
>     <owner>user</owner>
>     <security-constraints-ref>manager</security-constraints-ref>
>   </security-constraints>
> 
> and the page.security of the portal defines the manager ref as:
> <security-constraints-def name="manager">
>     <security-constraint>
>       <roles>manager</roles>
>       <permissions>view</permissions>
>     </security-constraint>
>   </security-constraints-def>
> 
> I'm making the assumption that this means the 'admin'/'manager' user (they
> have the 'manager' role assigned to them) could at least view the pages
> contained here, but when i'm logged in with this users and i try to view
> these pages with the link provided by the Portal Site Detail Portlet it just
> redirects me to the previous page i was before entering the Administrative
> Portlets.  Is this the way it is supposed to work?
> 
Yes

ALSO want to point out that the Portlet Selector will filter out 
portlets based on the permissions in the Jetspeed Security Policy.
Thus you can only add portlets that you have access to.
Its been debated whether we should also make this check during 
rendering, probably she be optional.

Im working on an XML version of the permissions for import/export, but 
for now the only way to edit this policy is to edit the database 
scripts. For example, this permission secures ALL the j2-admin portlets:

INSERT INTO SECURITY_PERMISSION 
VALUES(100,'org.apache.jetspeed.security.PortletPermission','j2-admin::*','view, 
edit','2004-05-22 16:27:12.572','2004-05-22 16:27:12.572');
INSERT INTO PRINCIPAL_PERMISSION VALUES(6,100);

Future version will support editing of these permissions via the 
j2-admin portlets

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org


Re: Administration and User Pages

Posted by Randy Watler <wa...@wispertel.net>.
Armando,

On Thu, 2006-02-16 at 12:50 -0500, Armando Arteaga wrote:
> Hi:
>   I have a problem with the security-constraints of Jetspeed2. I'm testing
> the deploy that comes with the installation package. First of all, i've
> looked everywhere in j2-admin portlets and there doesn't seem to exist a
> constraint manager per portlet like there was in jetspeed 1.x.

Some per portlet security functionality in J2 is still to come. At the
moment, there is a capability to constrain per Fragment in the PSML
pages and to restrict the ability to add portlets to a page using the
customizer. There is a proposal to add portlet level constraint and/or
permission checks to the aggregation process. Check the J2 JIRA issues
if you'd like to add some comments/requests:

https://issues.apache.org/jira/browse/JS2-354

>  Also I think
> there's no way to view the user pages with the manager or admin users.

The admin user can edit the pages in the j2-admin portlets, but they
cannot really "view" the page if it is user specific based on the
profiling rules. This is correct. However, when we improve the admin
pages, we may very well implement a preview mode or something like that
to allow the admin to see the page they are editing.

>   The
> folder.metadata in the user folder declares the security constraints as
> follow:
> 
> <security-constraints>
>     <owner>user</owner>
>     <security-constraints-ref>manager</security-constraints-ref>
>   </security-constraints>
> 
> and the page.security of the portal defines the manager ref as:
> <security-constraints-def name="manager">
>     <security-constraint>
>       <roles>manager</roles>
>       <permissions>view</permissions>
>     </security-constraint>
>   </security-constraints-def>
> 
> I'm making the assumption that this means the 'admin'/'manager' user (they
> have the 'manager' role assigned to them) could at least view the pages
> contained here, but when i'm logged in with this users and i try to view
> these pages with the link provided by the Portal Site Detail Portlet it just
> redirects me to the previous page i was before entering the Administrative
> Portlets.  Is this the way it is supposed to work?

See above. The permissions here do grant access as you would expect,
(plus there is the global permissions in page.security that grant the
admin user full access no matter what), but the profiler does not allow
you to view the user's page as it would appear in the portal. The page
is private.

In a nutshell: the profiler picks pages based on the request url and
security further restricts the pages that can be viewed: constraints and
permissions cannot override the profiler page selection.

There is the possibility that we can invent a way to circumvent this
restriction, but I am not sure an admin should need to view the user
specific pages. Does the admin user then see the end user's preferences
and attributes? Please add a JIRA issue if you feel this is a functional
gap in the Portal Site/Profiler components.

> 
> PS: Sorry for my horrible english.

No need to apologize... it is quite good!

HTH,

Randy



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org