So, with that setup, we receive the following message. Keeping in mind that our original default settings were set with what we are now calling SITE1 and it is now under the applicationoverride. The IDP side is fine and sends us back to our SP side without issue.
The error below seems to indicate that after the first site is mapped as DEFAULT which is wrong, it then goes back to also being SITE1 and then finally back to default?
<b>2018-04-13 15:28:29 DEBUG Shibboleth.ISAPI [4488] isapi_shib: mapped https://customer1.app.com/ to default
2018-04-13 15:28:29 DEBUG Shibboleth.ISAPI [4488] isapi_shib: mapped https://customer1.app.com/secure/Login.aspx to site1</b>
2018-04-13 15:28:29 DEBUG Shibboleth.SessionInitiator.SAML2 [4488] isapi_shib: attempting to initiate session using SAML 2.0 with provider (urn:mace:incommon:site.edu)
2018-04-13 15:28:29 DEBUG Shibboleth.Listener [4488] isapi_shib: sending message (site1/Login::run::SAML2SI)
2018-04-13 15:28:29 DEBUG Shibboleth.Listener [4488] isapi_shib: send completed, reading response message
2018-04-13 15:28:29 DEBUG Shibboleth.ISAPI [4488] isapi_shib: mapped https://customer1.app.com/Shibboleth.sso/SAML2/POST to default
<b>2018-04-13 15:28:29 DEBUG Shibboleth.ISAPI [4488] isapi_shib_extension: mapped https://customer1.app.com/Shibboleth.sso/SAML2/POST to default</b>
2018-04-13 15:28:29 ERROR Shibboleth.ISAPI [4488] isapi_shib_extension: Shibboleth handler invoked at an unconfigured location.
shibsp::ConfigurationException
The system encountered an error at Fri Apr 13 15:12:26 2018
To report this problem, please contact the site administrator at support@ourapp.com.
Please include the following message in any email:
shibsp::ConfigurationException at (https://customer1.app.com/Shibboleth.sso/SAML2/POST)
Shibboleth handler invoked at an unconfigured location.
<br/><hr align="left" width="300" />
Sent from the <a href="http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html">Shibboleth - Users mailing list archive</a> at Nabble.com.<br/>