You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
Membership Enabled and Disabled Dates as of v1.5.0
- Membership assignments can have enabled/disabled dates where the membership might be enabled in the future, or disabled after a certain period of time
- This will soon be applicable to the new attribute framework and application permission management
- There is command line support for enabled/disabled dates, or on the simple membership update screen
- 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:
membership = group.getImmediateMembership(Group.getDefaultList(), subject, true, true);
membership.setDisabledTime(GrouperUtil.toTimestamp("2009/11/02"));
membership.update();
* Example configuration in grouper-loader.properties
#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 * * ?
* Example gsh call for testing
loaderRunOneJob("MAINTENANCE__enabledDisabled");