ISAPI

[Sunil]

Thanks Scott. For some reason I don't see your response in the thread but I
got it in my mail.

Anyways, at this confirms that the installation is good and the config in
IIS is also fine.

>That would probably mean the protection rules themselves are not correct,
>and/or the <Site> mappings are wrong

I am using the default Shibboleth config. Here is the site mapping 

    <InProcess logger="native.logger">
        <ISAPI normalizeRequest="true" safeHeaderNames="true">
            <Site id="3" name="perftest.test.com"/>
        </ISAPI>
    </InProcess>

So the value in "name" above is the website bindings host name. I guess this
is correct.
The request mapper config is 

    <RequestMapper type="Native">
        <RequestMap>
            <Host name="perftest.test.com">
                <Path name="/secure" authType="shibboleth"
requireSession="true"/>
            </Host>
        </RequestMap>
    </RequestMapper> 

Do you see any mistake in this?

>That's a good sign you've broken the configuration severely. I don't know
>what you're doing, but you've put that literal URL into the configuration
>somewhere inappropriate, and that isn't going to work.

Is this a different problem or the cause for ISAPI filter "not" working?

Thanks
Sunil 



--
View this message in context: http://shibboleth.1660669.n2.nabble.com/ISAPI-tp7591231p7591233.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.