Trouble configuring SP3 for multiple idps
Cantor, Scott
cantor.2 at osu.edu
Wed Oct 31 17:43:17 EDT 2018
I can't really explain why you have all those target properties set all over the place and it sure won't work like that. The /Shibboleth.sso path is reserved for the SP's use unless it's diverted into using some other reserved path, and pointing a browser to just that location does nothing. That's just a base path for constructing the real handler paths and would give exactly that error in every version.
/Shibboleth.sso/Login is a real handler, as are many other paths, but /Shibboleth.sso is nothing. That's why the old (and now obsolete) ISAPI extension triggers on /Shibboleth.sso/*. You can't point anything there at anything of yours. Not before, not now. The updated IIS 7 module doesn't require any special handling for that, it just intercepts the requests when it has to regardless.
As for native.log, either you upgraded and the log file is there or not as your permissions would dictate, or you installed from scratch and it's in the Windows event log now, as documented in the upgrade and release notes and the page on logging.
-- Scott
More information about the users
mailing list