P.S.
Is it really necessary to be the magician in order to make it?
In fact it should be very simple base operation, without which portal any
more a portal.
And it turns out on the contrary.
2006/9/21, Michael Boss <[EMAIL PROTECTED]>:
Hi All,
I somehow already asked this question here, but something does not
turn out in any way.
I have created a user (testuser), has assign to this user a group
(testgroup) and profile (group-fallback). Further has edited a
WEB-INF\pages\Public\public.psml:
<fragment id="ps-1000" type="layout"
name="jetspeed-layouts::VelocityTwoColumns">
<fragment id="ps-1001" type="portlet" name="rss::RSS">
<property layout="TwoColumns" name="row" value="0" />
<property layout="TwoColumns" name="column" value="0" />
<security-constraint>
<groups>engineering</groups>
<permissions>view</permissions>
</security-constraint>
</fragment>
Apparently from this code, the access to this portlet (rss) has the
group "engineering".
However strange this portlet is visible to the testuser, but on idea
should not.
If I rewrite condition so:
<security-constraint>
<groups>testgroup</groups>
<permissions>view</permissions>
</security-constraint>
It as does not work and the portlet will be visible to all users.
What is wrong here? Any idea?
Many thanks
Mark McCullough wrote:
> You have to define which psml's each group gets to see by dropping those
> psmls into the group folder in the pages directory. Then go to portal
admin
> and assign each group member the profile of 'group-fallback'.
> For example, you want group A to see portlet A under page A, and you
want
> group B to see portlet B under page A.
> -mark-
