comanage-dev - Re: [comanage-dev] domestication & groups
Subject: COmanage Developers List
List archive
- From: Digant C Kasundra <>
- To: Steven Carmody <>
- Cc: Tom Barton <>, comanage-dev <>
- Subject: Re: [comanage-dev] domestication & groups
- Date: Thu, 26 Feb 2009 14:29:54 -0800 (PST)
----- Steven Carmody
<>
wrote:
> At 3:25 PM -0600 2/25/09, Tom Barton wrote:
> >
> >Please focus for the moment only on confluence. And let's rule out
> >the case in which groups are provisioned into confluence's local
> >store. So confluence is using groups residing outside it (ldap or
> >grouper directly, say). What should happen when the user goes to the
> >group-admin screen in confluence?
> >
>
> In discussions with Atlassian's "Confluence Architect", he has said
> that it was a mistake to include those screens....
>
> My sense is that -- at least in Brown's case -- users should be
> presented with a screen saying something like "group membership
> administration is done using the MACE Grouper tool. Click here to
> enter MACE Grouper.".
I agree. At least given the maturity of products at the moment, it seems to
me that changes to federated data must be made at the source of record. Until
we have achieved that "win," bidirectionality in this type of scenario maybe
too complex to be feasible.
--
Digant C Kasundra
Technical Lead, ITS Unix Systems and Applications, Stanford University
- domestication & groups, Tom Barton, 02/25/2009
- Re: [comanage-dev] domestication & groups, Scotty Logan, 02/25/2009
- Re: [comanage-dev] domestication & groups, Steven_Carmody, 02/25/2009
- Re: [comanage-dev] domestication & groups, Digant C Kasundra, 02/26/2009
Archive powered by MHonArc 2.6.16.