Federated Identity Management for Research Collaborations - Terena

More documents

Recommendations

Info

Common Requirements"•!•!•!•!•!•!•!•!User friendliness"–! Many users use infrequently"Browser and non-browser federated access"Bridging between communities"Multiple technologies and translators"–! Translation will often need to be dynamic"Open standards and sustainable licenses"–! For interoperability and sustainability"Di$erent Levels of Assurance"–! When credentials are translated, LoA provenance to be preserved"Authorisation under community and/or facility control"–! Externally managed IdPs cannot fulfil this role"Well defined semantically harmonised attributes"–! For interoperable authorisation"–! Likely to be very di#cult to achieve!"21 May 12" Federated IdM, TAC, Kelsey" 6"
Requirements (2)"•! Flexible and scalable IdP attribute release policy"–! Di$erent communities and di$erent SPs need di$erent attributes"–! Negotiate with IdF not all IdPs – for scaling"•! Attributes must be able to cross national borders"–! Data protection considerations"•! Attribute aggregation for authorisation"•! Privacy and data protection to be addressed withcommunity-wide individual identities"–! We need to identify individuals"•! E.g. ethical committees can require names, addresses, supervisors to grant access "21 May 12" Federated IdM, TAC, Kelsey" 7"
Page 1 and 2: Federated IdentityManagement for !R
Page 3 and 4: Background"•! Issue of IdM raised
Page 5: Workshops"•! Documented common re
Page 9 and 10: Common vision statement"A common po
Page 11 and 12: Recommendations (2)"•! To technol
Page 13 and 14: Some di#cultiesexperienced "•! Sp
Page 16: ""Questions?"21 May 12" Federated I

Federated Identity Management for Research Collaborations - Terena

Create successful ePaper yourself

Delete template?

Save as template?