SP Metadata/Status

[Senthil Ramiah]

We were able to resolve this issue. There was a case mismatch between the
ISAPI Handler mapping extension and the handlerURL.
-Senthil



sramiah at aileronconsulting.com
Aileron Consulting LLC
Steering businesses in the right direction™
2111 Wilson Blvd., Suite 700
Arlington, VA 22201
Phone: 703 869 8592
Fax: 703 351 9292
http://www.aileronconsulting.com

On Mon, Jun 1, 2015 at 9:40 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 5/31/15, 6:18 PM, "users on behalf of Nate Klingenstein" <
> users-bounces at shibboleth.net on behalf of ndk at internet2.edu> wrote:
>
> >You probably have a rule in place that is accidentally triggering
> Shibboleth protection for the /Shibboleth.sso path.
>
> It's much more serious, you have to have a totally corrupted configuration
> that isn't able to deduce the requests are for handlers inside the SP, so
> you have to be virtualizing incorrectly, setting handlerURL wrongly,
> something along those lines.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150601/1dcf0c14/attachment.html>