GenericSetup handlers to restore Zope security to defaults
WARNING: Backup your ZODB before using this package!
The Zope 2 security framework is very powerful and one of it’s greatest strengths. A lot of it’s power comes from it’s flexibility. Exposing that power to site adminsitrators often ends up giving them enough rope to hang themselves with. This is exactly what the “Security” tab in the ZMI does.
In many cases, a site admin or consultant is faced with the daunting task of restoring all the security settings throughout the Zope object heirarchy in order to bring sanity and predictability back to the site. The collective.securitycleanup package provides GenericSetup handlers for restoring the role mappings and local roles back to their defaults. This handler can be used in combination with existing handlers to set role mappings and to re-apply workflow security settings to help start the process of security cleanup.
The clean up is performed on all ancestors including the Zope application root and by walking down the heirarchy to all descendants. This means all descendents of the context the handler is used on and all ancestors of the context including the root will be cleaned up. It will not clean up siblings or anything else that is not a direct ancestor to the context.
The clean up removes all permission settings stored on the instance which effectively restores them to code defaults. The clean up also removes all local roles except the “Owner” role for the user returned by OFS.interfasces.IOwned.getOwnerTuple() if already assigned.
Use of this tool will likely only ever be a starting point. So be sure to test thoroughly before deploying to your production server and backup your ZODB before using it.
Updated on 01 December 2008
Imported from Plone on Mar 15, 2021. The date for this update is the last modified date in Plone.