[pubcookie-users] Pubcookie-3.2.1beta IIS problems ("relay.pubcookie3"?)

[Paul Fardy]

I've upgraded our Pubcookie WebLogin server to 3.2 and it appears to be 
working fine.

Being in the ".ca" domain, we're anxious to get POST-based hand-off 
working. The relay mechanism was unstable for us and Opera (for one 
browser) won't share ".utoronto.ca" domain cookies as we need.

But the 3.2.1 IIS Filter is not working for us. The filter is 
activating on initial access to the protected directory and our login 
server logs the redirected request. But the return redirect sends the 
browser to a "page not found".

relay: https://WEBAPP.HOSTNAME/relay.pubcookie3?appsrvid=WEBAPP.HOSTNAME

Our setup is much the same as for the working 3.1.1 version. We've 
attempted to get the config out of IIS—with a "Save config to file". 
Though that doesn't show our Pubcookie config, it does appear that the 
".pubcookie3" extension has assigned PubcookieFilter.dll as a handler.

The term "relay": Is this related to the old relay code? Or should I 
read that as "redirect"?

The Apache config has a PubcookieLoginMethod directive. We cannot find 
its equivalent in the IIS GUI-based setup. What are we missing? In 
general, there appear to be slight mismatches between IIS parameter 
names and those of Apache. Are these mismatches documented... or 
necessary, for that matter?

Incidentally, is there a marker in the log files of the login server 
that I can use to see who's still using the GET/cookie login method? 
I'd like to know that, ... eventually. :-)

Thanks for your time,

Paul
-- 
Paul Fardy
Computing and Network Services
University of Toronto
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1642 bytes
Desc: not available
Url : http://mailman1.u.washington.edu/pipermail/pubcookie-users/attachments/20050609/53d5f023/attachment.bin