Skip to Content.
Sympa Menu

comanage-dev - Re: [comanage-dev] domestication & groups

Subject: COmanage Developers List

List archive

Re: [comanage-dev] domestication & groups


Chronological Thread 
  • From:
  • To: Tom Barton <>, comanage-dev <>
  • Subject: Re: [comanage-dev] domestication & groups
  • Date: Wed, 25 Feb 2009 16:54:26 -0500

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.".

... and if Grouper were configured to use two SOURCEs (brown community, and the set of externals created by CoManage -- whoever that info is stored) then the user could add + remove people from their group....



Archive powered by MHonArc 2.6.16.

Top of Page