InCommon Library Services

[David Kennedy <>]

>I think of EZP as having two parts: a front-end
and a proxy.
>
>The front-end includes this sequence of steps:
>                
-- a way to configure whether the destination is shib-enabled 
>or not. If the destination is shib-enabled, the user is forwarded 
>there directly, bypassing the proxy.

I think it is important to point out that, when the
user is forwarded there
directly, they are also bypassing the normal WAYF
process
of the destination, as long as the destination has
properly implemented
SessionInitiators.



>One suggestion I've heard is that it makes sense to define a 
>persistent url for a provider as pointing to the EZP front-end. This
>would insulate the url from changes if the vendor moves from 
>IP-access control to Shib access control. Does this idea make sense?

YES