Versions Compared

Old Version 24

changes.mady.by.user Emily Eisbruch (internet2.edu)

Saved on

compared with

New Version 25

changes.mady.by.user Jeffrey Williams (uncg.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Adding in changeLog.enabledDisabled.queryIntervalInSeconds

...

  • Membership assignments and attributes/permissions can have enabled/disabled dates where the assignment might be enabled in the future, or disabled after a certain period of time
  • Enabled/disabled dates are supported through the UI, web services, and gsh.
  • The Grouper loader daemon is required for processing the registry periodically to set the enabled/disabled flag based on dates
  • Here is the Jira issue 

  • Example of assigning these via GSH:

    Code Block
    
membership = group.getImmediateMembership(Group.getDefaultList(), subject, true, true);

membership.setDisabledTime(GrouperUtil.toTimestamp("2009/11/02"));

membership.update();

    * Example configuration in grouper-loader.properties

    Code Block
    
#quartz cron-like schedule for enabled/disabled daemon.  Note, this has nothing to do with the changelog
#leave blank to disable this, the default is 12:01am, 11:01am, 3:01pm every day: 0 1 0,11,15 * * ?

changeLog.enabledDisabled.quartz.cron = 0 1 0,11,15 * * ?

#number of seconds between checks for changes in enabled/disabled status

changeLog.enabledDisabled.queryIntervalInSeconds = 3600

    * Example gsh call for testing

    Code Block
    
loaderRunOneJob("MAINTENANCE__enabledDisabled");


  • Enabled/disabled dates are called Start and End Dates in the UI.

...