Grouper Users - Open Discussion List

["Bee-Lindgren, Bert" <>]

Drew,

You are going to want to use a group-provisioning template as described in Carey's link. This will generally do the right thing and certainly should prevent objectclass violations.

The question I have is what you want the gidNumber and uidNumber of the group objects to be?

a) Normally, gidNumber will come from Grouper, eg, ${group.idIndex}. 

b) [Assuming you didn't mean memberUid] I'm not sure what uidNumber should be in your environment.RFC2307 [snippet below] indicates that you'll have to add another objectclass to define uidNumber. And then you'll need to find a value in the grouper group to define it. Let us know a little more and we can help.

( 1.3.6.1.1.1.2.2

 NAME 'posixGroup'

 DESC 'Standard LDAP objectclass'

 SUP top

 STRUCTURAL

 MUST ( cn $

  gidNumber )

 MAY ( userPassword $

  memberUid $

  description )

 X-ORIGIN 'RFC 2307' )

Sincerely,

  Bert Bee-Lindgren

---

From: <> on behalf of Black, Carey M. <>
Sent: Friday, June 2, 2017 3:53 PM
To: Drew Zebrowski;
Subject: [grouper-users] RE: Attribute Based Provisioning - PSPNG

 

Drew,

 

I think you are not looking at this the right way. ( But I am not an expert at grouper or specifically the PSPNG part.)

 

If you have not bumped into this page, it looks relevant.

REF: https://spaces.internet2.edu/display/Grouper/Grouper+Provisioning%3A+PSPNG#GrouperProvisioning:PSPNG-POSIXGROUPS

Grouper Provisioning: PSPNG - Grouper - Internet2 Wiki

spaces.internet2.edu

Provisioning's job is to reflect Groups and their Memberships in other systems. Over the years, dozens of provisioners have been created -- some focused on a single ...

 

Specifically I think this looks “wrong” to me.

“

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeName = gidNumber

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeValueFormat = ${new(java.util.Random).nextInt()}

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeName = uidNumber

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeValueFormat = ${new(java.util.Random).nextInt()}

“

You are trying to insert random integers for the gid and uid for the user. I doubt that is really what you want. ( on every “provisioning” of the user/groups.)

 

 

 

 

My guess is that you would want to assign a value ( using grouper to be the “authoritative source”) then send those values out to the connected system(s).

                REF: https://spaces.internet2.edu/display/Grouper/Getting+started+with+hooks2  (Note: this is circa 2011… YMMV )

Getting started with hooks2 - Grouper - Internet2 Wiki

spaces.internet2.edu

Hooks Example - Assign a UNIX ID to Each New Group. Hooks Introduction Getting started with hooks Proof of concept (A veto hook) - Assign a Unix id to each new group

                  “Hooks Example - Assign a UNIX ID to Each New Group”

 

                REF: https://spaces.internet2.edu/display/Grouper/Integer+IDs+on+Grouper+objects ( NOTE: circa 2012…. YMM Improve?, looks more civilized.

Integer IDs on Grouper objects - Grouper - Internet2 Wiki

spaces.internet2.edu

In Grouper 2.2+ the main Grouper objects in the database (groups, folders, attribute definitions, attribute names) will be assigned unique integers.

J )

                “In Grouper 2.2+ the main Grouper objects in the database (groups, folders, attribute definitions, attribute names) will be assigned unique integers.  These integers can be used, for instance, as UNIX GIDs.”

 

Hope that helps.

 

--

Carey Matthew

 

From: [mailto:] On Behalf Of Drew Zebrowski
Sent: Friday, June 2, 2017 2:44 PM
To:
Subject: [grouper-users] Attribute Based Provisioning - PSPNG

 

We are working on a way to provision posixAccount objectclass attributes for users and are looking at using Grouper to see if we can do this. I am new to Grouper and don’t have much experience with using the PSPNG component.

 

Here is our end-goal: Provision out the following attributes to an LDAP Person Entry.

 

-          Generate objectclass: posixAccount

-          Generate uidNumber: <Random Number>

-          Generate gidNumber: <Random Number>

 

In grouper-loader.properties, I tried the following which defines multiple attribute/value pairs. It doesn’t appear as though Grouper handles this since the LDAP returns an ObjectClass Violation.

 

# User gidNumber Provisioning

changeLog.consumer.pspng_secsds_gidNumber.class = edu.internet2.middleware.grouper.pspng.PspChangelogConsumerShim

changeLog.consumer.pspng_secsds_gidNumber.type = edu.internet2.middleware.grouper.pspng.LdapAttributeProvisioner

changeLog.consumer.pspng_secsds_gidNumber.quartzCron = 0 * * * * ?

changeLog.consumer.pspng_secsds_gidNumber.retryOnError = true

changeLog.consumer.pspng_secsds_gidNumber.ldapPoolName = secsds

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeName = objectclass

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeValueFormat = posixAccount

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeName = gidNumber

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeValueFormat = ${new(java.util.Random).nextInt()}

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeName = uidNumber

changeLog.consumer.pspng_secsds_gidNumber.provisionedAttributeValueFormat = ${new(java.util.Random).nextInt()}

changeLog.consumer.pspng_secsds_gidNumber.userSearchBaseDn = cn=users,o=tjuh

changeLog.consumer.pspng_secsds_gidNumber.userSearchFilter = uid=${subject.id}

 

 

Is this a supported function of the loader? Can it provision objectclasses along with the required attributes through the attribute provisioner or is this not designed to work that way? Has anyone done this sort of thing and is willing to share their experience? Thanks.

 

Drew Zebrowski

Thomas Jefferson University

 

The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.