Shibboleth Developers

["RL 'Bob' Morgan" <>]

Obviously we pitch an ease-of-use story with the WAYF setting a cookie to
remember "where you're from" so you don't have to interact with it after
the first time.  Unfortunately at least as currently implemented it's not
"where you're from" but "where you've told the WAYF you want to go".  In
testing, if I, say, choose one of the origins that isn't running now (like
mine), then a cookie gets set and that's it, I have no other chance to
interact with the WAYF, so I have to close my browser.  Now I happen to be
the sort of person that keeps a browser running on my laptop for weeks at
a time, with a dozen windows open, so closing is unpleasant.  I know
enough to be able to go in and delete the wayf cookie, so I can work
around it.

Obviously there's a longer-term issue of how to manage this interaction,
but I wonder if there isn't even a shorter-term problem that will cause
problems for pilots.  "Make a mistake, restart your browser"  isn't the
sort of impression we'll want to have the system make, especially since
poking around via the WAYF may be exactly what people do as part of trying
it out.  The only thing I can think of is to have the WAYF take the
cookie-provided value as a default and go-there-in-N-seconds if the user
doesn't choose another origin.

 - RL "Bob"


------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--