[Grok-dev] Workaround to disable admin-UI PAU

Uli Fouquet uli at gnufix.de
Mon Aug 20 11:20:03 EDT 2007

Hi Grokkers,

as Philipp already mentioned, it was not a good idea to copy credentials
from ZCML for the PAU of the admin-UI. My apologies for this!

I am already working to implement an alternative AuthenticatorPlugin
with a fallback to the base authentication.

For all you guys that ran into permission trouble of any kind: to
disable the PAU you might go into the debugger and do it by hand. The
PAU is placed in the root site mananger, is called 'authentication' and
has a PrincipalFolder 'Users' to hold the principals.

However, on restart the admin-UI might try to reinstall the PAU once it
was unregistered and deleted.

All this is setup in grok/admin/__init__.py.

As a quick and dirty workaround I could imagine something like this:

Index: src/grok/admin/__init__.py
--- src/grok/admin/__init__.py  (Revision 78996)
+++ src/grok/admin/__init__.py  (Arbeitskopie)
@@ -84,6 +84,9 @@
     from zope.app.authentication.principalfolder import

     sm = root_folder.getSiteManager()
+    sm.unregisterUtility(name=u'', provided=IAuthentication)
+    sm.unregisterUtility(name=u'Users', provided=IAuthenticatorPlugin)
+    return
     if auth_foldername in sm.keys():
         # There is already a folder of this name.

There might be better solutions, but so you know, where to look for
problems. I would consider to disable the PAU generally, until it is
better tested.

Again my apologies and kind regards,


More information about the Grok-dev mailing list