Skip to Content.
Sympa Menu

comanage-users - Re: [comanage-users] Making members visible

Subject: COmanage Users List

List archive

Re: [comanage-users] Making members visible


Chronological Thread 
    < Chronological >      < Thread >
  • From: Scott Koranda <>
  • To: Duncan Brown <>
  • Cc: "" <>
  • Subject: Re: [comanage-users] Making members visible
  • Date: Tue, 16 Nov 2021 07:37:05 -0600
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=illinois.edu; dmarc=pass action=none header.from=illinois.edu; dkim=pass header.d=illinois.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=h659u0kKcDNtR0jtb6FcEGvCWB5m2o8P2jg9ZZFBjd0=; b=DHexo5v2agbLouFHdeloWSB7WTtuP55nj+2SEmXBiaEBGxS3WohgKzfrVu1MXEI1wUxlbdChvQPBTVu2mDQsoJfRoLpu3Bz0yq8cY3Qg52cT+UI9Xy77SHLDH7qXWgH7j/aBxK1L1XtmtnaM5Yylp6Qp6BSRuWUBtWoK//l90cy0Gub8MwbIEyqoSwX6vSVIxgmz0+kDqueXDfbrAsQb5GEReVUdY/LySLZmtdQJIs6yFTzIGer/QHTkn72h3ugwHP0227UEsZg82hzhkGM37lIE8ezHet09Fv0AwEVTyUukc/juIQ4K/JT7cd1Gb/y4tbW2UKk+gP7/if7vxrebOw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MjazyS/QDuD1ipgemdnVzzVw/fhpi96A8iVx19xi2tmeaXFufj0sE2Fjhm3l2zMHNDmbKEOT3uW7SB5UHpj8wWGLQybbtjqxDBleLYfqSYJM0k0uFmk0TtVoV8cVQsEA0CrepRMERrjjL1JEqexmRFRIlLQ0KGNxsP7gZxwvICgQUXy61guCNFJ75s9v4P6cQaVXFKUAdsBN48xTORjL18TT+Y7Y82iSoz8a2jnh7wXnQeulHTRW2/2Gfb+6Klsq0DjnmovmgFoiZbek3z6XDAk7CSzoHh8yJadcDv2PkEct62WyR/2CWDuUgiNSFSdceonqawaxwLvfQUTatV7fKw==
Hi Duncan,

Comments inline below.

> Thanks, this is 3.3.x as I haven't had chance to upgrade
> roster.cosmicexplorer.org<http://roster.cosmicexplorer.org> to 4.x
> yet.

We expect 4.0.1 to be released "real soon now". It has some bug fixes
you will want. If you want to upgrade now I would build a new image
against the hotfix-4.0.x branch in GitHub. You can do that when you
build the image by setting

COMANAGE_REGISTRY_VERSION=hotfix-4.0.x

Otherwise I would wait for the 4.0.x release.

> If I view the group CEConsortium, I can see the members. I think my
> mistake is trying to view CO:members:active as a regular user. If I do
> that, I get permission denied (see screenshot). If I view the regular
> group CEConsortium group as a regular user, then I can see the
> membership.

That sounds as designed.

> The reason I tried to look at CO:members:active was that CEConsortium
> also contains users in "Pending Confirmation" and "Duplicate" status
> as my enrollment flow adds people to this group. I can probably just
> go in as the CO admin and remove those people from that group to clean
> it up, though.

Yes, though perhaps if you need a group that only has active users in
it, say for access control to some resource, you could created a
"nested" group and tick the box "Require All for Nested Memberships".
You can make one of the source groups be

CO:members:active

Then the user will only be in the new nested group if she is active and
in the group that you drop her into during enrollment.

See

https://spaces.at.internet2.edu/display/COmanage/CO+Groups+and+Group+Memberships#COGroupsandGroupMemberships-NestedGroups

You will want to upgrade to 4.0.x to use that functionality.

> BTW, I discovered a couple of gotchas in the mailman docker images
> that you may already have seen: psycopg2 needs to be pinned to 2.8.6
> and dnspython needs to be pinned to 1.16.0.

Thanks. I am going to start a private thread to discuss the Mailman 3
docker images (though if anyone on this list is really interested just
drop me a note and I am happy to include).

Cheers,

Scott

Archive powered by MHonArc 2.6.24.

Top of Page