Alert.png 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"

From EGIWiki
Jump to navigation Jump to search
 
Line 15: Line 15:
== LSDMA (German HGF initiative)  ==
== LSDMA (German HGF initiative)  ==


*[http://unity-idm.eu/ UNITY IDM]
*[http://unity-idm.eu/ UNITY IDM] developed within PLGrid


== Yet Another Virtual Organization Manager (YAVOM) ==
== Yet Another Virtual Organization Manager (YAVOM) ==


*[https://tnc2013.terena.org/getfile/95 TNC 2013 Paper]
*[https://tnc2013.terena.org/getfile/95 TNC 2013 Paper]  
*[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]
*[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>  
 
== Perun ==
 
*[http://perun.metacentrum.cz/web/ Perun]
 
== Feature matrix ==
 
This is an initial set of features that tools should support. I&nbsp;am sure that there will be more. Please add columns as needed.
 
{| width="200" border="1" align="left" cellspacing="1" cellpadding="1"
|-
! scope="row" | Service
! scope="col" | VO like group management (fix term)
! scope="col" | Supports SAML&nbsp;ECP
! scope="col" | Supports multiple Backend IdPs
! scope="col" |
! scope="col" |
|-
! scope="row" | SARoNGS
|
|
|
|
|
|-
! scope="row" | SLCS
|
|
|
|
|
|-
! scope="row" | TCS
|
|
|
|
|
|-
! scope="row" | LSDMA/UNITY
|
|
|
|
|
|-
! scope="row" | YAVOM
|
|
|
|
|
|-
! scope="row" | oAuth
|
|
|
|
|
|-
! scope="row" | Perun
|
|
|
|
|
|}

Latest revision as of 17:20, 5 February 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)

oAuth

I doubt that oAuth by itself serves the intended purpose.

Perun

Feature matrix

This is an initial set of features that tools should support. I am sure that there will be more. Please add columns as needed.

Service VO like group management (fix term) Supports SAML ECP Supports multiple Backend IdPs
SARoNGS
SLCS
TCS
LSDMA/UNITY
YAVOM
oAuth
Perun
Retrieved from "https://wiki.egi.eu/w/index.php?title=Federated_AAI_Survey_of_Credential_Services&oldid=64276"