Internet2's Trust and Identity in Education and Research (TIER) initiative aims to build on and extend these investments, integrate existing community-developed solutions and enable participants to better provide and access services, both on- and off-campus.

TIER funding in Internet2 funds Grouper development.  The funders help pick the direction of Grouper development. 

TIER release 1 which coincided with Grouper v2.3 focused on packaging up the TIER components which include Grouper, Shibboleth, and COManage, into images and containers.

Grouper is packaged as what the installer delivers on a MySQL database.

The instructions handed over the packaging team to setup the applications are here

See the TIER packaging site for more information and download links

Future work includes using Shibboleth for UI authentication, configuring provisioning, user management with COManage, having an upgrade/patch process, etc.

Running the current VM

• https://docs.google.com/document/d/1GUUyZIH5TWW2SkzDbFtApJrGrJlRlJKRpSDw_1qoDr0/edit?usp=sharing

• Get the current VM: https://s3-us-west-1.amazonaws.com/internet2-tier-appliance-us-west-1/grouper-appliance-centos7-ova-1473894412.tar
  
  

  [appadmin@i2midev1 opt]$ cd /opt/tierpackaging/
  [appadmin@i2midev1 tierpackaging]$ wget --no-check-certificate https://s3-us-west-1.amazonaws.com/internet2-tier-appliance-us-west-1/grouper-appliance-centos7-ova-1473894412.tar
  [appadmin@i2midev1 tierpackaging]$ tar xvf grouper-appliance-centos7-ova-1473894412.tar

• Setup networking in VM in virtualbox
  
  General settings
   

  
  
  

• Settings for that VM
  
  
   

• Follow instructions in the README.md

• 
  
  
  

Discussion with Levvel August 1st, 2016

• We will have 3 containers
  • Loader
  • WS
  • UI
• Grouper will continue externalizing configuration so that the subject api and ehcache use configuration properties overlays
• Properties files can be mounted outside the container and specified via env variables
• UI/WS will come with tomcat and apache and ready for shib SP
• Containers will be built with latest patches
  • The container maker can look at release notes page for latest release to see list of patches available

Testing a Grouper container

• At a minimum hit the status servlet on the UI and WS, get a 200 back.  /status?diagnosticType=all
• Note the grouper daemon needs to have been running for a minute or two
• Look at the UI, login, see the Grouper UI, click around a little
• Make a grouper client call to the WS, make sure you get a positive result