Grouper enabled and disabled dates

Membership Enabled and Disabled Dates as of v2.0.0

• 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
• 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");
  

See also the Overview of Access Management Features page for guidelines of when to use rules, roles, permission limits, and enabled / disabled dates.