The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Federated AAI Survey of Credential Services"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
*[https://tnc2013.terena.org/getfile/779 TNC 2013 Presentation] | *[https://tnc2013.terena.org/getfile/779 TNC 2013 Presentation] | ||
*[https://tnc2013.terena.org/getfile/481 Another TNC 2013 Presentation] (almost like the previous one) | *[https://tnc2013.terena.org/getfile/481 Another TNC 2013 Presentation] (almost like the previous one) | ||
*[https://indico.egi.eu/indico/materialDisplay.py?materialId=slides&confId=2001 Hexaa project presentation in FedCloud call on 2014-01-21] | |||
== oAuth == | == oAuth == | ||
I doubt that oAuth by itself serves the intended purpose.<br> | I doubt that oAuth by itself serves the intended purpose.<br> | ||
Revision as of 11:12, 22 January 2014
This survey of credential services shall guide the decision about which technologies, implementations, or mechanisms to use for federated AAI. Generally speaking, the question is which implementations support certain IdP mechanisms, most preferably Shibboleth, as the eduGAIN inter-federation is based on that.
UK SARoNGS shibb to x509 crededntial translator using myproxy
SWITCH solution (SLCS?)
TCS by Terena
LSDMA (German HGF initiative)
Yet Another Virtual Organization Manager (YAVOM)
- TNC 2013 Paper
- TNC 2013 Presentation
- Another TNC 2013 Presentation (almost like the previous one)
- Hexaa project presentation in FedCloud call on 2014-01-21
oAuth
I doubt that oAuth by itself serves the intended purpose.