Grouper Users - Open Discussion List

["Bryan E. Wooten" <>]

Ah, so it seems if loader.ldap.requireTopStemAsStemFromConfigGroup = true in 2.1.3 then I get that extra colon.

 

Time to upgrade.

 

Thanks,

 

Bryan

 

From: Chris Hyzer [mailto:]
Sent: Tuesday, June 11, 2013 10:24 AM
To: Bryan E. Wooten;
Subject: RE: : Can't find stem by name: ':uofu:ref-groups'

 

Are you using 2.1.4?  there was a tweak put in there April 18^th… if you have a grouper.jar after that it should work… J

 

Thanks,

Chris

 

From: [] On Behalf Of Bryan E. Wooten
Sent: Tuesday, June 11, 2013 12:10 PM
To:
Subject: [grouper-users] : Can't find stem by name: ':uofu:ref-groups'

 

Whenever I run my Loader ldap job I get the following error:

 

Caused by: edu.internet2.middleware.grouper.exception.StemNotFoundException: Can't find stem by name: ':uofu:ref-groups',

 

When I run this in gsh I get the stem:

 

gsh 6%  stem = StemFinder.findByName(grouperSession,"uofu:ref-groups")

stem: name='uofu:ref-groups' displayName='University of Utah:Reference Groups' uuid='a3b34fac5759444b92054bdda75c75cf'

 

So apparently the issue is the ‘:’ in front of the “uofu”. I can’t for the life of me figure out where that colon is coming from.

 

In grouper-loader.properties I have this:

 

# by default the top folder for an ldap group of groups is the folder where the config group lives.

# set to false if you want to be able to provision groups to anywhere

loader.ldap.requireTopStemAsStemFromConfigGroup = false

 

My loader job has this for the ldap group name _expression_:

 

uofu:ref-groups:${groupAttribute}

 

Where is that colon coming from?

 

Thanks,

-Bryan