Grouper attestation means marking a group or folder so that owners must review the membership list periodically.  This is useful in ad hoc groups where deprovisioning is not automatic.  Owners will be reminded by email to review the memberships.  After reviewing the memberships, the group owner will click a button on the group indicating that it has been reviewed.

This is in the 2.3.0 API and UI patch (TODO list patch number) 

How to use:

• At the start up time, attestationDef and attestationValueDef attribute definitions will be added to the system as shown in the screenshots. 
• You will notice a new menu item Attestation in the More actions dropdown for groups and folders as shown in the screenshots:  
• When you click on the Attestation menu item and there are no attestation attributes for that group/folder and any of the parents in the hierarchy, you will see a screen which has a link to configure the attestation for that group/folder. Here is the screenshot: 
• Clicking on the link will take you to the screen where you can add the attestation attributes. Here is the screenshot:  Each attribute is described in detail in the Design section below.
• If attestation attributes already exist for a group or any of the stems in the parent hierarchy then they are displayed like shown in the screenshot. 
• If the logged in user is a member of the wheel group or has admin privileges on the group, they can edit the attestation attributes.

Design

• Under "more actions" button on groups and folders, have an "Attestation" option above "View audit log"
• Users who have Wheel, Admin or Read/Update should see that option
• This will go to a page for attestation for that group (looks like "copy" screen with breadcrumbs, name, then the attestation screen part)
• If there is no attestation for that object or parent folders, display "No attestation configured"
  • To see if there is attestation, check the object for an attribute, if not there, check parent folder, if not there, parent folder, etc.  First attribute assignment wins

  • Use this method to check if has attestation (it implements that algorithm)
    
    

    groupOrFolder.getAttributeDelegate().hasAttributeOrAncestorHasAttribute()

• If there is no attestation for that object, but there is inherited attestation, display which (closest) parent folder has the attestation and describe it
• If there is attestation on that object, describe it, allow Admins of the group (or wheel members) ability to edit the attestation
• For Group, for Wheel, Admins, or Read/Update, if there is attestation (direct or inherited), have a button that says "Members of this group have been reviewed". On click, if there is no attestation attribute, add it.  Add/update the attestationDateCertified to today's date.  Note, if there is no attestationDirectAssignment attribute, add it and set to false...
• When the UI is used to assign attestation, have a checkbox which says “Update the last certified date for this group to today’s date” or “Update the last certified date for this folder’s groups to today’s date”
• On the folder screen have a button that says “Certify this folder’s groups”  (updates all relevant groups attestationLastCertified value to todays date”
• On the folder screen have a button that says “Certify this folder’s uncertified groups” (updates all relevant group which have neverbeen certified)
• If there is no direct attestation, for Wheel, and admins, have button "Configure attestation for this group" (or folder)
• If multiple ancestor folders have attestation, use all configuration from the closest folder.  If a group has attestion (direct), use all configuration from the group only (no folders)
• Attributes on folders, groups:  (two attributeDefs) (note, autocreate these attributeDefs and attributeNames on startup)
  • attestation (main flag, other attributes assigned to this assignment, no value, single assign)
    • attestationDirectAssignment (true | false) (on group only) default to false.  If true then dont look at a folder for attestation attributes
    • attestationSendEmail (String, true | false)  default to true if not set
    • attestationEmailAddresses (String) comma separated email addresses to send reminders to.  If not set, then get email addresses from list of Admins and Read/Update users.  Note, we need a param (in the source) of which subject attribute is the email attribute.  If none sent, log error, need either emails here or emails from admins
    • attestationDaysUntilRecertify (String) integer number of days until need to recertify from last certification.  Can have a default in grouper.properties if not set. (180?)  
    • attestationLastEmailedDate (String)(on group only)  yyyy/mm/dd date that this was last emailed so multiple emails dont go out on same day
    • attestationDaysBeforeToRemind (String) Integer number of days before attestation to start sending emails about it.
    • attestationStemScope (String) one|sub (for folders only, scope one level or all levels).  Default to all levels.
    • attestationDateCertified (String) (on group only) yyyy/mm/dd is the last date certified for this group.  (only for groups, not stems) 
• Edits to the screen should generate attestation specific audits
• Daemon should run daily (via cron) and look for groups which have not been attested.  Should group by email address.  Send each user who get an email their own email with a list of groups and linked to be attested.  Remind the user about clicking the button saying it is certified.

• Email logic:  Take each email to each user (by email address), and only send one email to that user.  Ff there are more than 100 (configured in grouper.properties) attestations, just show 100 in the message but say there are 5432 others so email isn’t too big. Also, add at the bottom of each message who was CC’ed since you email will be sent directly to a person.

  e.g.

  school:groupA needs attestation: emails to: jsmith@school.edu, and bgreen@school.edu

  school:groupB needs attestation: emails to: jsmith@school.edu, and kwilson@school.edu 

   

  send 3 emails:

  FIRST EMAIL:  To jsmith@school.edu 

   

  Subject: you have 2 grouper groups that require attestation.

  Body: 

   

  You need to attest the memberships of the following groups: 

   

  1. 1.       school:groupA   (cc’d bgreen@school.edu)

  <link to membership> 

   

  1. 2.       school:groupB (cc’d kwilson@school.edu)

  <link to membership>

  
  

  SECOND EMAIL: To bgreen@school.edu 

   

  Subject: you have 1 grouper groups that require attestation.

  Body:

  You need to attest the memberships of the following groups:

   

  1. 1.       school:groupA   (cc’d jsmith@school.edu)

  <link to membership>

  THIRD EMAIL:  To kwilson@school.edu 

   

  Subject: you have 1 grouper groups that require attestation. 

  Body: 

   

  You need to attest the memberships of the following groups: 

   

  1. 1.       school:groupB (cc’d jsmith@school.edu)

  <link to membership>

• Future scope
  • If attestation is not done in a certain amount of time, disable the memberships or group somehow
  • Have screen that shows all attestation assignments in the registry (which folders and groups have the attestation flag)
  • Have screen that shows all groups that need to be attested with their status.  If there are too many groups, then have a search for them, or maybe select parent folder?
    • Be able to filter this by groups that are overdue for certification