grouper-dev - Re: [grouper-dev] GRP-304 AKA MCO-4...challenging oldest issue fix
Subject: Grouper Developers Forum
List archive
- From: Tom Zeller <>
- To: James Cramton <>
- Cc:
- Subject: Re: [grouper-dev] GRP-304 AKA MCO-4...challenging oldest issue fix
- Date: Thu, 29 Oct 2009 20:30:43 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=CvsPb/Ewk9xB4aYZ1wGvkBcBAEJxg8+JKskoBoZ+R9KurCoIKPV/2P/r11amKudzgN 4byxkGkVquOpQkqdRwY8c/zWYAE7t1Z7POUzVXPBb/b+60HudEv8LVocglSSMIJfGdgb Tvx65ZUNUmA7By3kCc/44L8OjVN9GEOA/pV1s=
> Sorry I missed yesterday's call...I meant to ask a question about GRP-304,
> which I submitted a few months ago, and is the same as the issue I reported
> 2 years ago--MCO-4. Kathryn intended to address it in LDAPpc 1.1.1, but it
> didn't make it into a release.
>
> Was this issue fixed in Grouper 1.5, and is just not tagged as such?
>
> I'd hoped to offer Tom Z the incentive of challenging Shilen's 'oldest issue
> fix' title, but I see Shilen's fix beats MCO-4 by a couple months. It was
> worth a shot.
Fixed enough for 1.5.0. I've updated jira.
By default, ldappc 1.5.0 will only provision member groups which are
in the set of groups to be provisioned, i.e. match group-queries.
There is a configuration option to revert to pre-1.5.0 behavior. The
on-not-found="ignore" option would also help eliminate voluminous
logging if the pre-1.5.0 behavior is desired.
This is still not as good as I would like, but SPML2 style
provisioning will have to wait for now.
TomZ
- GRP-304 AKA MCO-4...challenging oldest issue fix, James Cramton, 10/29/2009
- Re: [grouper-dev] GRP-304 AKA MCO-4...challenging oldest issue fix, Tom Zeller, 10/29/2009
Archive powered by MHonArc 2.6.16.