Shibboleth Developers

still *very drafty*

There are several areas we'd like to cover:

-- the broad concept of "the user experience in a multi-federation 
world", including:
        -- navigation (in a multi-federation word)
	-- error handling -- particularly providing appropriate 
responses in a variety of error situations
        -- support for deep linking
        -- support for the use of bookmarks accessing shib-enabled resources

1) Navigation

Current situation -- from off-campus, essentially all users must come 
in via the local library pages, in order to find and traverse the 
local campus proxy. Otherwise... the user will not be able to access 
the resource, and no navigation help is provided. The Shibboleth 
"direct to target" model is brand new....

Possible approaches include:

-- a single universal WAYF of WAYFs
        - who would run?
        - how would it be governed?
        - would require an *incredible* level  of robustness
        -- how does this relate to some sort of global discovery service?

-- vendors could each do their own WAYF
        -- collect metadata from X number of federations
        -- filter with their customer list
        -- present this list to the browser user
	-- contact central  cache to SET IdM (how to SET in a 
multi-federation world)

-- have vendor present a "provider page", with Athens and a list of 
Federations

-- question of lightweight vs heavyweight WAYF/cache protocol

-- (what is the value/cost of creating an SSO among the vendors)

2) Error Handling

There are a number of different errors that can occur, and care 
should be taken to present appropriate error screens:

--  user selects wrong identity provider...

-- user comes from a site that does NOT have a business arrangement with SD

-- user comes  a site that does have a business arrangement with SD, 
but presents the wrong attributes