SP handlerURL modification not working

[Peter Schober]

* Brent Goebel <Brent.Goebel at du.edu> [2021-04-02 22:12]:
> I am trying to setup SSO with Ellucian Banner Document Management
> (Application Xtender). I’m using Shibboleth SP (v. 3.1.0.1) with
> it. Ellician requires the Assertion URL to be in the following
> format

What code is supposed to process the SAML Response/Assertion, then?
If that's application code then how's the Shib SP involved?
If it's the Shib SP why should the application care at what URL the
Shib SP processes the SAML? It should only care about how the Shib SP
forwards that information to the application (headers, etc.).

> handlerURL="/AppXtender">

Even by changing the handlerURL prefix that's not going to let you
create arbitrary ACS URLs, does it? Even if this setting this worked
I'd expect the final ACS URL for the SAML2 HTTP-POST binding to be
/AppXtender/SAML2/POST, not /AppXtender/BdmSamlSso (nor /AppXtender).

> I go to the metadata URL (https://<hostname>/AppXtender/Metadata)
> and the metadata does not populate.

What exactly does "the metadata does not populate" mean? What exactly
is being returned at that URL?
Are you even talking to the Shib SP at the URL /AppXtender and not to
your application?

-peter