Configure Shibboleth-SP-2.3.1 with DS-1.1.3.

[Cantor, Scott]

> Default use might never hit /Shibboleth.sso/Login with active session
> protection. If you can access that URL directly, then there's no reason it
> would start returning a 404 because you add the DS into the mix.

Another thing to check is if it's Apache returning the 404 or something else like Tomcat if it's a Java application. Since /Shibboleth.sso/SAML2/POST or what have you can't be failing with a 404 if the SP were working, perhaps something is selectively letting Apache handle that path, but breaking other handlers such as /Login.

-- Scott