<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Courier New">Thanks Scott.<br>
<br>
The /etc/httpd/conf.d/shib.conf has been changed with the upgrade.<br>
This block has been added with the update:<br>
<br>
#<br>
# Ensures handler will be accessible.<br>
#<br>
<Location /Shibboleth.sso><br>
Satisfy Any<br>
Allow from all<br>
</Location><br>
<br>
I just simply removed it and worked.<br>
My question is: Why the use of Satisfy Any when the login handler is on
/Shibboleth.sso/Login? My drupal site points its login handler to that
location. If that Satisfy Any directive is there, it cannot
authenticate.<br>
<br>
Thanks,<br>
Pedro.<br>
<br>
</font><br>
On 02/07/2013 16:55, Cantor, Scott wrote:
<blockquote
cite="mid:BA63CEAE152A7742B854C678D949138394600771@CIO-KRC-D1MBX01.osuad.osu.edu"
type="cite">
<blockquote type="cite">
<pre wrap="">I believe there are differences (even minor ones) that would affect
this. If I downgrade to 2.5.1-1.2 it works without changing any
configuration files. (I only keep the /etc/shibboleth/shibboleth2.xml
across versions).
</pre>
</blockquote>
<pre wrap="">
The only thing I can think of is that you didn't modify shib.conf at all, in which case the upgrade would change that file, specifically adding a Location block for /Shibboleth.sso with commands to guarantee that nothing blocks access to the handlers inadvertently. That's the area to check, and I would simply remove the modification and see if that matters. I have no idea why or how it would.
-- Scott
--
To unsubscribe from this list send an email to <a class="moz-txt-link-abbreviated" href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a>
</pre>
</blockquote>
</body>
</html>