Grouper Users - Open Discussion List

["Bryan E. Wooten" <>]

David,

 

Can you be more specific about “custom psp name”?

 

Are you saying I need create a custom class for this in grouper-loader.properties:

 

#specify the consumers here.  specify the consumer name after the changeLog.consumer. part.  This example is "psp"

#but it could be changeLog.consumer.myConsumerName.class

#the class must extend edu.internet2.middleware.grouper.changeLog.ChangeLogConsumerBase

changeLog.consumer.psp.class = edu.internet2.middleware.psp.grouper.PspChangeLogConsumer

 

Thanks,

 

Bryan

 

 

 

From: David Langenberg [mailto:]
Sent: Wednesday, October 02, 2013 4:10 PM
To: Bryan E. Wooten
Cc: Chris Hyzer;
Subject: Re: [grouper-users] Syncing Groups between 2 Groupers

 

changeLog.changeLogTempToChangeLog.enable = false  yes

 

the next one about the cron shouldn't matter.

 

You're on the right path.  On number two though, you need to change the name of the PSP stuff to a custom psp name.

Dave

 

On Wed, Oct 2, 2013 at 3:33 PM, Bryan E. Wooten <> wrote:

So let me see if I understand this. 2 Grouper Daemons one runs the change log the other doesn’t

 

The first Daemon runs a psp that provisions AD and the other Daemon runs a psp that provisions LDAP.

 

At this point isn’t the second Daemon just a platform to run a change log consumer (in this case the psp).

 

So I should be able to just set the change log daemon to run on the second daemon to sometime far into the future?

 

# should the change log temp to change log daemon run?  Note, this should be true

changeLog.changeLogTempToChangeLog.enable = false

 

#quartz cron-like schedule for change log temp to change log daemon, the default is 50 seconds after every minute: 50 * * * * ?

#leave blank to disable this

changeLog.changeLogTempToChangeLog.quartz.cron = * * * * * 2525

 

Am I on  the right path?

 

-Bryan

From: Chris Hyzer [mailto:]
Sent: Wednesday, October 02, 2013 3:19 PM
To: David Langenberg; Bryan E. Wooten
Cc:
Subject: RE: [grouper-users] Syncing Groups between 2 Groupers

 

I think that is the best way to go... if we need to tweak the loader to not run the change log or something, that should be doable I would think...

---

From: [] on behalf of David Langenberg []
Sent: Wednesday, October 02, 2013 4:15 PM
To: Bryan E. Wooten
Cc:
Subject: Re: [grouper-users] Syncing Groups between 2 Groupers

Sebastien Gagne was attempting this with 2 separate grouper-loader daemons.  Did you ever get that working Sebastien?

 

Dave

 

On Wed, Oct 2, 2013 at 2:07 PM, Bryan E. Wooten <> wrote:

Since I just can’t seem to get the PSP to provision both AD and LDAP I think this may be a workable solution.

 

Here is my plan, let me know what you think.

 

1.       Master Grouper

a.       This has the Loader and Web UI

b.      Pushes stems, groups and members to Slave Grouper

c.       PSP provisions to Active Directory

d.      LDAP Subject Source

e.      Grouper Loader loads groups from Active Directory

2.       Slave Grouper

a.       Has the Web Service installed

b.      Has the Loader

c.       LDAP Subject source

d.      PSP Provisions to LDAP

 

Users only manage Groups on the Master Grouper using the WEB UI. The Slave Grouper’s sole purpose in life is to provision Groups in LDAP, otherwise it is a mirror of the Master Grouper.

 

Thanks,

 

Bryan

 

--
David Langenberg

Identity & Access Management

The University of Chicago

 

--
David Langenberg

Identity & Access Management

The University of Chicago