Some thoughts on the e-Infrastructure requirements for supporting Virtual
Organisations.
A Virtual Organisation (VO) is one that intersects with multiple real
organisation. It is comprised of users from multiple home
institutions. Many of which may be entirely unaware of the existence
of the VO at all. This means that the Virtual Organisation needs to
be self-organising and must be provided with the tools to manage its
own membership.
One of the potential problems we have identified with AuthN tools like UK-Federation and Moonshot is that they (for good reasons) generate a different identifier for each service domain.
I've had several conversations this week that related to what's commonly referred to as "level of assurance": how confident we can be that an account or other information about an on-line user actually relates to the person currently sitting at the keyboard. Governments may be concerned with multiple forms of documentary proof but I suspect that for most common uses in the education sector that may be over-complicating things.
In discussions with e-Infrastructures we’ve spoken quite a bit about federated authentication, so I thought it was worth a quick summary of the federated authentication schemes already available on Janet. And, in particular, what the policies of those federations already offer to Service Providers by way of guarantees.
