Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

This is a design document for deprovisioning support in Grouper.  Comments welcome.

Deprovisioning in Grouper allows a deprovisioning administrator to see someone access and instantly remove it.  It would also help notify application administrators where grouper is not the system of record.

  1. The Grouper UI could have a one-pager for deprovisioning.
  2. Users of this screen would need to be in a certain group.  Grouper admins would also be allowed to use this page
    1. Note: users of this screen would effectively have a lot of access in grouper.  They can pull up any subjects and see what they have.  They can remove most things.  But they do not have to be Grouper admins.  This screen could be used by an HR person.
  3. This screen could be disabled if an institution does not want it.
  4. The screen would start with a subject lookup for someone to be deprovisioned
  5. When submitting that combobox, all the assignments in grouper would display, as well as deprovisioned status
  6. A button "Add to deprovision group" could add the user to a preset group for people who will be deprovisioned.  
    1. This group should have a membership expiry for a certain amount of time (1 month is the default)
    2. This group can be used in "exclude" groups or rules in grouper
    3. Note, some institutions might already have this "lockout" group
  7. Assignments on screen will include memberships, privileges, permissions, and attributes(?)
  8. The screen will have checkbox about assignments to deprovision
  9. There could be a way to see effective as well as immediate assignments, though it will default to immediate (ones you can deprovision)
  10. There will be a "check all" and "uncheck all" button
  11. An "unassign" button will remove all those assignments
    1. All assignments could be stored temporarily in attributes so that the state could be restored (future feature if people interested)
    2. At the very least, the stuff unassigned could be logged and emailed to the user using the app so they could piece it back together.  Maybe grouper import script or GSH?
  12. Groups and folders could have attributes related to deprovisioning
    1. Mark a group or folder as ineligible for deprovisioning (e.g. the lockout group)
    2. Mark a group or folder with attributes so that emails are sent out to application owners to deprovision that user.  This would not remove the assignment in grouper because in this case grouper is not the source of the assignment but instead reflects it in another system.   The receiver of the email would need to unassign the user and that data would flow back to grouper ater the next load
      1. e.g. an attribute to say "deprovision_notify_app_owner", an attribute "deprovision_notify_app_owner_email", attribute "deprovision_notify_app_owner_email_subject", "deprovision_notify_app_owner_email_body"
      2. Attribute keep track of when last emailed
  13. There could be a feature in loader jobs to not load deprovisioned users (without having to adjust the query).  Of course loader jobs could be exempt from this if they need deprovisioned users inside.  The default would be to not include them
  14. There could be an overall audit and then keep individual audits
  15. There could be a report of deprovisioned users and assignments they still have access to so that followups can be made after a week or two to make sure everything is removed for that user that should be
  16. There could be a report of inactive users and things they are still assigned to to clean out users who left the institution long ago
  17. Set membership expire dates based on required groups (potential)
  18. Remove membership expire dates based on adding back in to required groups (potential)

 

  • No labels