[pubcookie-users] Problem with Pubcookie and zope/plone
cristopher pierson ewing
cewing at u.washington.edu
Thu Mar 29 13:06:57 PDT 2007
I am working on setting up a server running zope/plone behind an apache
proxy using pubcookie for authentication. I've gotten this setup to work
on a development server, so I know the instructions should work, but on
the new server I'm running into a problem.
My server is an Intel Mac XServe running OSX Server 10.4.9
I'm using Apache 2.2, and pubcookie 3.3.2c, downloaded and compiled fresh
on Tuesday this week (two days ago).
Pubcookie authentication works perfectly in the simple test case of a
folder in my apache document root protected by .htaccess file.
Following the instructions at http://www.washington.edu/webinfo/case/zope/
I have built and installed apache mod_fba as a DSO, enabled mod_fba with
the appropriate directives in all my <VirtualHost> sections, enabled proxy
with the appropriate rewrite conditions and rules in each <VirtualHost>,
added the appropriate RequestHeader directive to each <VirtualHost>, set
up Auth using <Location> sections in my main httpd.conf file, compiled and
installed LOGIN.c as directed, and restarted apache. I've also added a
CACSiteRoot to my zope instance, configured zope to accept passwordless
logins, and prohibited access to zope from all but the localhost.
Interactions with the server at this point take the following course:
1. I request my server's URL from some machine:
2. I am served the zope introductory page, as expected
3. I click on the link to the Zope Management Interface (which should be
4. I am forwarded to the pubcookie login page where I log in using my
UWNetID and password.
5. The pubcookie server redirects me back to my server where I get stuck
on the following page request:
and am greeted by an Internal Server Error message (HTTP 500).
Looking into the access, error, and ssl_request logs for the server reveal
that it is the 'POST PubCookie.reply' request that is going awry, but
there are _no_ errors shown in the error log whatsoever. I am unsure of
how to proceed in trying to debug this.
I've posted more about this problem to www-mgmt, the folks who maintain
the case study cited above, but I figured since this looks like a problem
with pubccookie, I might start here with trying to get some help.
Any ideas on where to go from here?
CME and Telehealth Web Services
Department of Radiology Web Services
University of Washington
School of Medicine
Work Phone: (206) 685-9116
Home Phone: (206) 365-3413
E-mail: cewing at u.washington.edu
More information about the pubcookie-users