COmanage Developers List

[Niels van Dijk <>]

 Hi Benn,

Some other considerations for the last scenario:
- The role of the user in the VO may differ between universities (member
in one, admin in the other)
- Blue and Brown might want to be able to identify their staffs
contribution to the VO.
- Working at Brown may offer access to different services within the VO
then when working for Blue (e.g. both uni's may have a different system
to register time spend, though both systems may be part of the same VO)
- If you choose to support this scenario you must somehow combine IdP
attributes of both IdPs. I do not believe there are any readily
available mechanisms to do that.

For now we (within COIN) choose to 'ignore' this scenario and assume
every identity is unique. We do not map or combine identities from IdPs
in any way. We also feared many SPs would not be able to handle complex
or combined identities in a sensible way

Cheers,
Niels

On 10/12/2010 09:40 PM, Benn Oshrin wrote:
> The scenario of a person being affiliated with a source institution in
> order to have membership in a VO is well described.
>
> We've also discussed a person switching affiliation but wanting to
> maintain VO membership.  (eg: They were affiliated with Brown
> University, but are now affiliated with Blue University.)
>
> What about someone being multiply affiliated?  For example, they are
> part time faculty at Brown University and part time faculty at Blue
> University.  Does the VO need to know both of these affiliations, or
> is one sufficient?  If the former, why?
>
> -Benn-