SP handlerURL modification not working

[Peter Schober]

* Brent Goebel <Brent.Goebel at du.edu> [2021-04-03 00:07]:
> Ellucian  is saying that the Consumer Assertion URL needs to be
> https://<hostname>/AppXtender/BdmSamlSso. So on their application
> they are looking for this URL format.

The only way this makes any sense is if they are acting as SAML SP and
will be decoding (and possibly decrypting) and processing the SAML
themselfs. Which is fine, it just doesn't have anything to do with
(and there'd be no need for) the Shibboleth SP software.

You can probably use their application (and whatever SAML 2.0 WebSSO
support that comes with it) with the Shibboleth IDP ("Identity
Provider") software, if you're running that. Maybe someone is
confusing those two.

> I already asked if they could modify their application code to take
> https://<hostname>/Shibboleth.sso/SAML2/POST and they there is no
> way to edit the expected Assertion URL on the application side. It
> has to match this AppXtender/BdmSamlSso.

Then I guess that's simply their SAML endpoint. Feed that to your SAML
IDP and forget about the Shibboleth SP.

-peter