Shibboleth Developers

["Alistair Young" <>]

> stop trying to offload discovery
> do it in
> the application where the decision can be made with the most information
sorry, that's what I thought you meant by the application, the SP. But the
decision will made in the DS. Which is offloading...

You recommend the DS should make the decisions, not the SP. Though in an
ideal world the SP should provide a box for the hapless user to type what
they think is their IdP URL.

Alistair


-- 
mov eax,1
mov ebx,0
int 80h

>> When I referred to "web service" (and all that that can mean) I was
>> contrasting with Scott's view that the SP should do all the discovery
>> leg
>> work, which isn't SOA compatible. I think that's what he was saying.
>
> I did *not* mean that the SP should do all of it. I meant that the SP
> shouldn't send the browser somewhere else (logically speaking) to do it.
>
> If you think it's viable to build a web service to do it for the SP, by
> all
> means have at it.
>
> Note that the Shibboleth SessionInitiator is pluggable, as all the
> handlers
> are. One could implement one that did such a thing.
>
> -- Scott
>
>
>