issue with IIS application integration

[Liam Hoekenga]

I'm working with a vendor who has never used the SP...

Their .NET application lives at /app/.
/app/ is set to be protected in shibboleth2.xml, but requests for /app/ do
not actually invoke the SP handler.

The app developer assigned to the integration keeps wanting to manually
redirect to https://vendor.com/Shibboleth.sso/Login to initiate the login
process.  I've only ever triggered session initiation by accessing a
protected path.  Should an app ever trigger the session initiator directly?

I added /secure/ - which is just a folder w/ an index.htm file
I added that path to the host definition in shibboleth2.xml and bounced
iis, and requests for /secure/ DO invoke the sp.

One of our local IIS admins suggested to check and make sure that the
version of .NET is the same as the version of the ISAPI filter (32bit vs
64bit).

Any other suggestions?

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161220/dcad7b67/attachment.html>