Shibboleth Developers

[Olivier Salaün - CRU <>]

That would indead be a usefull feature to have a hierachical 
organization of IdP sites on the WAYF web page. This means that the 
sites.xml DTD should evolve to store these additional hierarchical 
informations...

This change to the WAYF GUI is not enough though because in most cases 
(at least in France), a web resource is not widely opened to all 
Universities ; it is rather restricted to some "partner" universities. 
In such situations, the user is not aware of this restriction, it is up 
to the SP to define this list of IdP sites. You still need to have 
multiple WAYF services either at the SP level or et a level where it is 
shared by a group of universities.

Sassa wrote:

> Scott Cantor wrote:
>
> > > [...]
> >
> > Exactly, the latter especially. That's my point. Proliferating WAYFs 
> > is why ultimately the SP has to deal with this.
>
> If the problem is that the list is too long, why can't WAYF categorize 
> the sites, so the user would have two options: look through the whole 
> list, or tree walk the categories and sub-categories. In essence, WAYF 
> can be an LDAP browser, and the users choose:
> [...]

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature