Child pages
  • Grouper enabled and disabled dates
Skip to end of metadata
Go to start of metadata

Membership Enabled and Disabled (Start/End) Dates as of Grouper v2

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

Using the LITE UI to set Start and End Dates

Enabled/disabled dates are called Start and End Dates in the LITE UI.  For information, see the LITE UI - Part 2 training Video (minute 5.53).

See Also

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

  • No labels