SP v4 alpha2 testing

[Scott Cantor]

> There's probably something really basic missing ? Is it trying to
> figure out SP's entityID or AssertionConsumerService Binding ?

The latter. It's crashing in the logic I built to allow for the legacy "style" of the old SP where each binding has its own location at the SP, and the way that works is that the Agent feeds in a list of details to the Hub about the paths and the bindings.

I presume (from the key discussion) you also probably uncommented the support for the legacy handlers in handlers.ini, and something there must be broken. I tested it (and have unit tests in fact) but something's going wrong in there so I'll have to re-test all that.

Most of our testing is with the newer endpoint convention (/Validate for everything) and it doesn't run that code.

I started out with the plan that maintaining the old conventions was important and then realized that retaining keys was going to be a dead end at scale, which made the rest kind of pointless.

But it should work, I'll figure out what's going on.

The actual bindings it picks from are specified in the Hub and don't generally need to be changed, since you always want POST anyway.

-- Scott