...

• It provides more reliability
  • As a service / resource you have certainty about the identity
  • If an employee leaves an organization and may therefore no longer have access to a service / resource, federative authentication ensures that access is no longer possible.
• It ensures scalability
  • As a service / resource you have no / less work on creating an account, supporting users who forget their password etc
• It increases security
  • Users can use their (strong) settings password and do not have 'another' account and password to manage
  • Users only have to enter their password on the settings-login screen known to them (the fewer deviating screens ask for passwords, the less sensitive users are for phishing)
• It ensures user-friendliness
  • With only 1 already existing and known username / password can use more services and no / less extra separate log-in data

The European AARC-project has a training-module on what a identity federation is and what its advantages are: Federation-101.

Will this be a SURF service?

...