Shibboleth SP browser loops when attempting to connect to protected site

[Cantor, Scott]

On 8/8/14, 2:51 PM, "String76" <hortonb at kayacorp.com> wrote:

>Sorry about the last reply.  Did not intend to reply without adding more
>details.  In the host section I was under the impression the Path name
>should be set
> to the site/application you want to protect?

Yes, that's true. The Site mappings are not part of that section, and your
Site element is just wrong.

>  EmpWeb is an application under the ShibTest site.  I thought that for
>Shib to work I had to point to
>
>https://iometer1.kayacorp.com/EmpWeb/Shibboleth.sso

No. /Shibboleth.sso is a trigger via file extension for a script mapping
to the ISAPI extension DLL that handles functions supplied by the software
like the SAML ACS. It has nothing to do with your content apart from
needing the share a virtual host with it for cookies purposes. If the root
of the site is off limits for that purpose, then other things have to
change to transplant the handlers to a different location. The only
apriori reason to move it is to host multiple application overrides on a
single vhost.

-- Scott