embedded Java SP

[Cantor, Scott]

> I know well the history of the Java SP (that's not what I'm referring
> to here) but has there ever been any talk about implementing the bare
> minimum SP functionality in the IdP software to preclude the need for
> new IdP deployments to use TestShib.

No, the discussion has really been to do one for proxying. The problem with "minimal" is that it's a fantasy. One person's unnecessary feature is just another's core need. Ultimately it's an SP and requires resources to support another SP. The only thing it doesn't need for proxying, practically speaking, is a lot of session and application mapping features, which is admittedly the bulk of my SP, but the rest isn't nothing.

> I mean, every IdP deployment needs a dedicated SP anyway, so why not bundle one with the Shibboleth
> IdP software?

I don't think it's practical to build something that would be targeted at proxying but somehow use it in the opposite direction, but I'm sure it's possible.

But the answer to why not is the same as always, money and time. testshib is not a drain on the project because we ignore it.

-- Scott