comanage-dev - Re: [comanage-dev] Multiple source institution use case?
Subject: COmanage Developers List
List archive
- From: Tom Barton <>
- To:
- Subject: Re: [comanage-dev] Multiple source institution use case?
- Date: Fri, 15 Oct 2010 08:59:57 -0500
Yes, that's one way to meet the reporting requirement. Teragrid
essentially operates this way, for example. Another is to rely on a
common, external source of identity: IGTF blessed PKI in this case,
which meets both requirements (but of course has other downsides).
Maybe we should consider an approach to the issue Benn raised which
separates the means to maintain user identification (ensuring continuity
of identification, if that's what's desired) from the means to report
and manage access across services. Basically an account linking model, I
suppose, in which one account in maintained by users for themselves and
others are VO, CO, or campus-specific. Maybe even PGP-like, with
signatures signifying linkages.
Tom
On 10/15/2010 4:45 AM, Niels van Dijk - SURFnet wrote:
> Hi,
>
> Could we imagine a VO setting an attribute to define a unique identity
> throughout the VO? Is that something the VOs are already doing, perhaps
> in the Grid world?
>
> cheers,
> Niels
>
>
> On 10/14/2010 09:58 PM, Tom Barton wrote:
>> Some science grids have reporting needs, and perhaps access management
>> needs, that oblige them to know who someone is apart from where they
>> come from. That need leads to two requirements: one like Steve mentioned
>> in AU, in which diverse resources (SPs) across the grid need to know who
>> someone is and correlate their use of resources across the grid, and the
>> other is to preserve their access regardless of their home institution.
>>
>> The Bamboo project is formalizing requirements in this area now, and it
>> appears they will likewise have similar needs.
>>
>> Tom
>>
>> On 10/12/2010 2: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-
>
- Re: [comanage-dev] Multiple source institution use case?, (continued)
- Re: [comanage-dev] Multiple source institution use case?, Steven Carmody, 10/12/2010
- Re: [comanage-dev] Multiple source institution use case?, Benn Oshrin, 10/12/2010
- Re: [comanage-dev] Multiple source institution use case?, Dan Pritts, 10/14/2010
- Re: [comanage-dev] Multiple source institution use case?, Michael R. Gettes, 10/14/2010
- Re: [comanage-dev] Multiple source institution use case?, Dan Pritts, 10/18/2010
- Re: [comanage-dev] Multiple source institution use case?, Michael R. Gettes, 10/14/2010
- Re: [comanage-dev] Multiple source institution use case?, Dan Pritts, 10/14/2010
- Re: [comanage-dev] Multiple source institution use case?, Benn Oshrin, 10/12/2010
- Re: [comanage-dev] Multiple source institution use case?, Niels van Dijk, 10/12/2010
- Re: [comanage-dev] Multiple source institution use case?, heather flanagan, 10/12/2010
- Re: [comanage-dev] Multiple source institution use case?, Steven Carmody, 10/14/2010
- Re: [comanage-dev] Multiple source institution use case?, Tom Barton, 10/14/2010
- Re: [comanage-dev] Multiple source institution use case?, Niels van Dijk - SURFnet, 10/15/2010
- Re: [comanage-dev] Multiple source institution use case?, Tom Barton, 10/15/2010
- Re: [comanage-dev] Multiple source institution use case?, Niels van Dijk - SURFnet, 10/15/2010
- Re: [comanage-dev] Multiple source institution use case?, Steven Carmody, 10/12/2010
Archive powered by MHonArc 2.6.16.