Shibboleth Developers

[Chad La Joie <>]

In the present, where browsers are SAML illiterate, I don't think you 
can ever get to the point where the user isn't shown some WAYF function 
(either as a standalone page or as part of the SP).  I think the cookie 
method I described can make sure that in the majority of use cases the 
user won't actually have to select anything (i.e. the correct IdP will 
be preselected).  Cases where this wouldn't work would be if the browser 
had never participated in a Shibboleth transaction, the cookie had 
expired, or the user of the browser is from a different organization 
than normally uses the system (i.e. a visitor at Georgetown who is from 
Univ. of Washington).

I know that Rod and Scott had talks about creating SAML aware plug ins 
for various browsers, if that work proceeds and is fruitful (which I 
have no doubt it will be) then you can probably make the WAYF stuff 
disappear almost all the time.


 wrote:
> > Now, supposing that all our 2500 participants join Shibboleth, how 
> > we're going to make that WAYF navigable is a really good question.
>
> rephrasing Spencer's question -- what can we do so that users 
> never/rarely see the WAYF?

--
Chad La Joie             315Q St. Mary's Hall
Project Sentinel         202.687.0124