Error: ISAPI extension can only be invoked to process Shibboleth protocol requests

[Cantor, Scott]

On 6/20/14, 12:24 PM, "Alvarez, Dyana I" <d.alvarez2 at miami.edu> wrote:

> 
>I noticed it's a common error and found some threads which I perhaps need
>to check:
> 
>Check if you have configured the following in the shibboleth2.xml
>1. Site Id with correct id and name (IP address) OK
>2. Handler with correct IP address and context - NOt sure what this means
>the HandlerURL?

The error means the request to a *.sso resource is deducing a handlerURL
that doesn't match the request. Any request to *.sso is considered a
handler request, so the request must deduce that it itself is the right
handler for that request.

For example, if you access https://host/foo, it deduces
https://host/Shibboleth.sso as the handlerURL base. If you access
https://host/Shibboleth.sso/whatever, it also deduces that
https://host/Shibboleth.sso is the handlerURL base. If it were to deduce
something different in that second case, it wil throw that error.

>And this is all I have. I don't have ApplicationOverride to override any
>ApplicationID's or
>anything like that.

That's simplifying, but it means the site->host mappings aren't working
right.

> 
> 
>I also checked the Shib IdP logs, the native log in the SP and didn't
>find any errors.
>Perhaps I need to open up more DEBUG?

You'll need to DEBUG the native.log and see what the requests are mapping
to.

>I still don't understand what is the issue.
>I noticed someone talked about the part of the session tags, which I
>don¹t have the handleURL.
>I thought it would default to /Shibboleth.sso anyways.

It does.

-- Scott