...
Membership Enabled and Disabled (Start/End) Dates
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
This topic is discussed in the "Grouper Permissions" training video (see minute 8:33) and in the "LITE UI Permissions Part 3" training video. |
- 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 #suggested values are between 900 and 3600 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.
...