Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Admin UI Troubles

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Admin UI Troubles


Chronological Thread 
  • From: Chris Hyzer <>
  • To: Chuck Kimber <>
  • Cc: "" <>
  • Subject: RE: [grouper-users] Admin UI Troubles
  • Date: Wed, 25 Feb 2015 18:21:20 +0000
  • Accept-language: en-US

I think the loader will do what you want.  If you have a group all the way down the rabbit hole, it will create the intermediate folders for you.

 

Heres an example

 

https://spaces.internet2.edu/display/Grouper/Grouper+Loader+classlist+example+from+Penn

 

thanks,

Chris

 

From: [mailto:] On Behalf Of Chuck Kimber
Sent: Wednesday, February 25, 2015 12:39 PM
Cc:
Subject: Re: [grouper-users] Admin UI Troubles

 

On Wed, Feb 25, 2015 at 9:35 AM, Waldbieser, Carl wrote:


On a system with its own cron-like service, you can just set up a jon to fire off a GSH script to create folders based on some criteria.  Depending on your needs, it could be simple or complex.

 

This is pretty much how our current, non-grouper, system works.  So here is my use case:

 

We have some powershell that fires up on a scheduled task.  It runs some SQL to our Banner (ERP) system to find some things out.  For example, what terms are currently "active".  Based on that information we build OU's inside the Term OU.  Then inside each term's seperate OU we construct OU's for each type of term based groups, like Fee Groups and Course groups.  In our current usage, this is where we finally build our term based groups.  It might look something like this:

 

DistinguishedName : CN=201520 - 10001 - ACCT - 2010 - 001,OU=courseGroup,OU=201520 - Spring 2015,OU=studentTerms,OU=studentGroups,OU=ERP,DC=ourAD,DC=usu,DC=edu

 

So what I described is from the OU=studentTerms on up the chain till we finally have a group for accounting 2010, section 001  (And yes our names are very verbose with identifying numbers and names.  It seems t help with people designing ldap queries to have multiple filter options, or for the layperson)

OU=studentTerms

OU=201520 - Spring 2015

OU=courseGroup

CN=201520 - 10001 - ACCT - 2010 - 001

 

So what I was thinking is to auto-create all the sub OU's below the Student Terms OU and then finally create groups all the way down that rabbit hole.  Like I said, this is already happening in all our custom powershell foo, but it would be nice to replicate in Grouper so I'm not the only guy around that knows how to do it.  The SQL is already out there in Oracle as several functions and views that return records, so I'm hoping to just jack grouper into them and crank it up to 11!




Archive powered by MHonArc 2.6.16.

Top of Page