I hope this helps:
Quote from Werner Ramaekers [EMAIL PROTECTED]

<security-entry name="user_print">
        <meta-info>
            <title>User with Print</title>
            <description>Users that can have print friendly 
views.</description>
        </meta-info>
        <access action="*">
            <allow-if role="admin"/>
        </access>
        <access action="view">
            <allow-if role="user_print"/>
        </access>
        <access action="print_friendly">
            <allow-if role="user_print"/>
        </access>
    </security-entry>

Hope this helps

Werner

Brad Straw wrote:

>Has anyone been successful in developing a security role that only 
>allowed view and print-friendly portlet modes?  I would like to have 
>certain portlets to have the print-friendly option without the 
>customize and info icons as well.
>
>I've been able to develop custom security roles that only allowed view, 
>maximize, and minimize but I have not been successful with this 
>configuration.
>
>Thanks

-----Original Message-----
From: Pierre Henry [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 17, 2003 11:05 AM
To: Jetspeed User List (E-mail)
Subject: security : print action access

Hi !

I have defined a security reference with several acesses for different
roles. For the role user, I have to define several actions, but not all, so
I did one access for each action. They all work but one : the print action.
If I put the following access element, the print button doesn't appear on
the portlets.

<access action="print">
        <allow-if role="user"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="java:org.apache.jetspeed.om.registry.base.BaseSecurityAllow"/>
</access>

If i just change "print" to another action (eg. info, customize,...) it
works and the button doesn't appear. With print it doesn't...

This may be a bug. Has anybody met this behavior ? I didn't find any
bugzilla entry about that.

Greetings,

Pierre


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to