...
| Criteria | Without eduTEAMS | With eduTEAMS | |||
|---|---|---|---|---|---|
| Identity Management | |||||
| |||||
Account Provisioning | Accounts have to be created for each member of the research community, which requires collecting name, addresses, etc. beforehand. Keeping the user data up-to-date will required to periodically ask the users or their organisations for any changes, which is a unreliable and cumbersome process that will likely result in stale and inaccurate data within a few months. | Creating accounts on eduTEAMS Member Registration service can be as easy as having a list of email addresses with which participants are invited. Thanks to federated login via eduGAIN, accounts (incl. name, organisation and more) can automatically be created upon first login. Up-to-data user data from the user's home organisation is available on every consecutive login at a service, which easily allows service to always the the most up-to-data data. | |||
Credential Distribution | Credentials (passwords) have to be created, properly protected, distributed and reset by research community on their own. | Nothing to worry about because credentials are managed entirely by user's home organisation (i.e. university) | |||
| Identity Management | Keeping identities/accounts up-to-date has to be done by research community on its own, depending on architecture even multiple times on every application that is used collaboratively. | Identity management is done by users home organization or - in case the user uses the eduTEAMS Identity Hub - the the user himself. |
| ||
Credential Management | |||||
| Implementation Time | |||||
| Scalability | |||||
| Costs |
...