SOAP SLO handler: what would it be used for?
trscavo at gmail.com
Wed Apr 16 16:03:22 EDT 2014
On Wed, Apr 16, 2014 at 3:31 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> ... if you have that use case, you
> shouldn't need somebody to tell you that you do. This is why my original
> answer to this kind of question stands: you run the services you need, and
> only you can know what those are.
I pretty much know for a fact this is not the case. Deployers
typically bring up the full range of services available to the IdP
because Shibboleth has done such a great job making that so easy to
do. It's not because deployers need those features; more often than
not, they don't. In many cases, those extra features don't even work
as deployed. We know this is true with many ArtifactResolutionService
endpoints, for example.
I'm not suggesting the Project do anything differently. I suspect this
is mostly a federation issue. Our software pre-populates six text
fields with endpoint locations compatible with the standard Shibboleth
installation. We probably need to stop doing that.
> And any decision you make now has to be
> subject to future change when the answers change.
That's true of course but I'm not really understanding your point.
More information about the users