Date: Fri, 29 Mar 2024 15:31:22 +0000 (UTC) Message-ID: <151355507.8175.1711726282077@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8174_702279297.1711726282077" ------=_Part_8174_702279297.1711726282077 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The three-year TIER program reached a successful conclusion at the end o= f 2018. The program, funded by 49 investor schools, involved containerizing= and connecting the Internet2 Community=E2=80=99s key open-source Identity = and Access Management software components, significantly reducing the time = and effort needed for installation, configuration, and upgrades. The result= is the new InCommon Tr= usted Access Platform, an IAM suite meeting the specific needs of resea= rch and education. Please visit the InCommon Trusted Access Platform wiki for more information= , including links to software downloads.
TIER: Production R= eleases
The TIER team is grateful for&n=
bsp;everyone who evaluates and uses these releases.
Docker Containers
Docker Containers
=Release Notes<= /p>
Shibboleth SP Linux htt= pd Container (3.0.3)
Current release: 181201
Container Image Name: tier/= shibboleth_sp:3.0.3_181201
Status: New build of new SP major rev
Shibboleth SP Windows I= IS Container (3.0.3)
Current release: 181201
Container Image Name: tier/= shib-sp-windows-iis:latest
Status: New container
Grouper Linux Container= (2.4.0)
Current release: 2.4.0-a29-= u14-w3-p2-20190217
Container Image Name: tier/= grouper:2.4.0-a29-u14-w3-p2-20190217
Grouper Linux Container= (2.3.0)
Current release: 2.3.0-a109= -u47-w13-p24-20190208
Container Image Name: tier/= grouper:2.3.0-a109-u47-w13-p24-20190208
COmanage Linux Containe= r (3.2.0)
Current release: 20190101= span>
Container Image Name: tier/= comanage:3.2.0-20190101
<= span style=3D"color: rgb(165,173,186);">Container Source Code
Release Notes<= /span>
midPoint
Coming soon...
Virtual Machine Images= p>
The links below are to vir= tual machine images, which are designed to be Docker build/run machines and= are preloaded with the appropriate set of Docker containers. The VMs&= nbsp;are intended primarily for campuses that do not currently operate cont= ainer-based applications or are new to container-based applications. AMIs, = for running in AWS, are also available here.
Virtual Machine Images and Documentati= on
= COmanage Registry (3.1.1)
COmanage VM (1.3 GB)
= Grouper (2.3.0)
Grouper VM (1.0 GB)
= Shibboleth IdP VM (3.3.1)
Shibboleth VM (1.2 GB)
<= /li>Amazon Machine Images (AMIs)
Amazon Machine Images (AMIs)
If you will be using the r= eleased VMs, below are a few suggestions:
The VMs are designed to be =
run in VirtualBox. If you are not familiar with VirtualBox, you can r=
ead the documentation and download the software from the
AMIs, for running in AWS, a= re also available here.
=Once VirtualBox is installe= d and running, you import the .ova distribution using the File / Import App= liance function.
The default network connect= ion for some of the Virtual Machines is NAT. This works well if you wa= nt to log into and examine the VM and containers. But to connect to service= s hosted by the VM, you'll likely want to switch the network to bridged mod= e. This will give the VM an IP address from your network's DHCP server and = provide you with the ability to access services from a browser.
<= /li>Please review the Release N= otes for installation instructions and additional information on VirtualBox= setup.
Remember to change the logi= n password(s) before you place the VMs on a public network.
This document, TIER Accomplishments by Thematic Groups, provides the current = state of the component portions of the TIER program and planned future acti= vities. It draws from initial documentation of TIER program requirements = span>and subsequent working group accomplishments. It also includes items flagged =E2=80=9C[Must2018]=E2=80=9D which have been identified by the compone= nt architects as being required to be completed before the end of 2018.
Visit the TIER 101 page.
Starting with the 17040 release= , the TIER components contains functionality from phase 1 of the TIER Instrumentation work. = If you need to disable this functionality, you can configure a manual sett= ing in the local Dockerfile on the VM. There is a commented sect= ion near the top of the file that instructs you to uncomment a single line = below which will disable the TIER Instrumentation functionality.