1. Discovery and Federated Identity

2. Topics Life today and the pull-down list from Hell
Hints at the wrong layer suck
The importance of keeping the continuity of experience
Staying with the story
How does the likely path of interfederation affect discovery

3. Life Today Workarounds
Initiating at the IdP – e.g. PSU get to NIH through the PSU research web site.
Hand out Per-IdP URLs (e.g. Google)
Assume one IdP, "click here if you're a weirdo" in its login UI
Models
SP/Embedded – e.g .Elsevier
Centralized/Shared
SP-centric - e.g. NIH Federated Login gateway vs. federation/IdP centrice.g. WAYF, InCommon

8. Moving from /etc/hosts to interfederation
Connecting autonomous federations
Critical for global scaling, accommodating state and local federations, integration across vertical sectors
Has technical, financial and policy dimensions
Technical solutions include eduGAIN and MDX
Policy activities in eduGAIN, Kalmar2 Union, Kantara, Terena

9. MDX – metadata exchange protocol
Institutions and organizations will pick a registrar to give their metadata to
Institutions and organizations will pick an aggregator (or several) to get their partners metadata from
Aggregators exchange metadata with each other and registrars
If this sounds like DNS registration and routing, it is, one layer up

10. PEER Big Picture

11. Implications for discovery
So many IdP’s…
Can sub-select at the SP
Can get sticky at the SP
Discovery for non-web apps
Pop up a browser
Sticky on the device (cookie, cert,…)