Home › Support › Knowledge Base ›

Portlet Permissions Reset to Default

Knowledge Base: Academus, Academus 2.0, Academus 2.1, Blogger, Briefcase, Gateway, Notifications
Updated: June 18, 2007
Why are permissions for the Everyone group sometimes reset to their defaults when using the PortletPermissions portlet?
This is a known bug where the permissions are reset to the values specified in the portlet configuration files (briefcase-portlet.xml, messaging-portlet.xml, gateway-*.xml, etc.). The workaround is to specify the target and group name to something that doesn't exist (e.g. NOGROUP). This workaround will only work once the permissions for the Everyone group are persisted in the access_entry table.

This is an example of the briefcase portlet configuration:

<access-broker handle="notifications-p" impl="net.unicon.alchemist.access.jit.JitAccessBroker">
    <jit-rule>
        <behavior>
            <trigger type="GROUP">NOGROUP</trigger>
            <target type="GROUP">NOGROUP</target>
            <access impl="net.unicon.academus.apps.messaging.MessagingAccessType">
                <type handle="ATTACH" value="GRANT"/>
                <type handle="DELETE" value="GRANT"/>
                <type handle="COMPOSE" value="GRANT"/>
                <type handle="SAVE" value="GRANT"/>
            </access>
            <creator impl="net.unicon.alchemist.access.permissions.DummyCreator"/>
        </behavior>
    </jit-rule>

    <access-broker
        handle="notifications-p-i"
        impl="net.unicon.alchemist.access.rdbms.RdbmsAccessBroker"
        needsDataSource="true">
        <access impl="net.unicon.academus.apps.messaging.MessagingAccessType"/>
    </access-broker>
</access-broker>