Attribute Authorities - 20121120
Main Room | Backup Room | |
---|---|---|
Session 1 15:00-15:45 | Attributes on attributes... - 23rd | Rich clients and proxy as a solution - 23rd |
Session 2 15:45-16:30 | OpenID Connect love/hate - 23rd | IdP Discovery - 23rd |
Session 3 16:30-17:15 | Room 1 Session 3 | Room 2 Session 3 |
Topics
- TF-EMC2 needs a ToR, help me write it (Brook)
- Location, location, location (Brook)
- 1-Click™ Enablement of Service Provider (Klaas)
- OpenID Connect, should be fear or embrace it (Ajay)
- What is the "organisation" for a virtualised identity provider (Montonori)
- Office 365 and Rich Client Support in a federated environment, solved by proxies, can this scale to solve other problems (Joost)
- Attribute Options, where to dump this in SAML (Peter)
- Id as a Service, what's your experience (Roland vRW)
- Discovery Service, can we have 1 thing that is globally usable (Milan)
- Account Linking (Ken)
- Identity Linking (Lalla)
- "Standard" attribute translation from Grid to Federation, then back again (Lalla)
- As an SP, what's the business case for an attributeless IdP (Niels)
- How are we going to scale interfederation at a global scale, with the pieces we have (Niels)
- Attributes as 1st class citizens (Victoriano)
- Attributes on attributes (Roland vRW)
Discussion on attributes
Roland presented some use-cases that would require attributes being collected from different sources.
In some of the use-cases the IdP acts as a broker collecting attributes from different sources, whereas in some other scenarios the SP contact the IdP and the trusted AA to collect the attributes.