Grouper Users - Open Discussion List

[Scott Koranda <>]

> By default in 2.1.0, provisioning via the psp and the grouper change
> log is disabled.
> 
> Documentation for provisioning via the psp triggered by the grouper
> change log is here :
> 
>  https://spaces.internet2.edu/display/Grouper/Grouper+Provisioning
> 
> See the section currently, and perhaps sub-optimally, titled
> "Configure Grouper Change Log".
> 
> In general, in grouper-loader.properties, by default, the following is
> commented out - which means that the psp will not run :
> 
> # changeLog.consumer.psp.class =
> edu.internet2.middleware.psp.grouper.PspChangeLogConsumer
> 
> TomZ
> 
> https://spaces.internet2.edu/display/Grouper/Grouper+Provisioning#GrouperProvisioning-ConfigureGrouperChangeLog
> 

Thanks Tom.

I am still trying to understand the transition from 1.6.x
ldappc-ng to 2.1.0 PSP.

Is this a viable strategy?

- download, deploy, and configure PSP following instructions
  and one of the examples at

  https://spaces.internet2.edu/display/Grouper/Grouper+Provisioning

- run

  bin/gsh.sh -psp -calc stem:groupName

  to see if the calculation looks approximately correct, and
  then follow up with

  bin/gsh.sh -psp diff stem:groupname
  bin/gsh.sh -psp sync stem:groupname

  to effect a provisioning into LDAP and make sure the basic
  plumbing is working

- assuming a single group can be provisioned then run

  bin/gsh.sh -psp -bulkSync -interval 60

  and make sure that provisioning for all groups and
  memberships works

- turn off the bulkSync

- configure the Grouper daemon so that real-time provisioning
  is enabled and restart the daemon/loader with

  bin/gsh.sh -loader

  test to verify that changes in Grouper propgate to LDAP in
  "real time"

- turn on bulk sync again but with a larger interval, say 15
  minutes, so that it can clean up any orphans

Can I be certain there will be no bad side effects from
running both the loader with "real time" provisioning turned
on and the bulk sync, i.e. no flapping?

Thanks,

Scott