Thanks for responding.

The multi-plugin was written by Cris (cc'd above) here at UW. The plugin isn't incredibly invasive, and in fact at one point it seemed to be working so I tend to assume that it may be a configuration/installation/human error. If you'd like to take a look at it, I've copied a tarball and the extracted contents out to for perusal. We've done a fair amount of debugging to the plugin and haven't found a blaring error yet, but it is possible we missed something.

The main problem that we seem to be having seems related to the context of the installation - if the plugin is installed at the zope root acl_users folder, only users listed in that folder with the manager role will have their permission reflected on all plone sites underneath. If the plugin is installed under a plone site's acl_users folder, users with the manager role in that site have the proper permissions, but root level managers (ie zope admins) will have a limited set of rights - once the plugin is enabled for the final plugin type, trying to view all available plugin types again (/<SiteName>/acl_users/plugins) will result in a list of Undo options instead of the expected Plugin Types.

Thanks again,

Tres Seaver wrote:

Hash: SHA1

Michael Gilbert wrote:

We are currently having problems trying to get authorization working with Plone 2.5.2, Zope 2.9.6, and Python 2.4.3 using pubcookie and a multi-plugin to communicate with pubcookie. We've verified that pubcookie is working properly and that user names are getting passed on to Zope, but the right roles are not assigned to the deserving users. Below are the steps to repro the problem:

Where is the multi-plugin coming from?  It is likely the source of your

- --
Tres Seaver          +1 540-429-0999          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


Zope-PAS mailing list

Reply via email to