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

Compare with Current View Page History

« Previous Version 152 Next »

As of Grouper v2.5+ it is required to use the InCommon Trusted Access Platform packaging approach.


Report Grouper Security Concerns here

View the Grouper Demo

View the Grouper demo  (if you have issues registering for the demo, click here for info)

Current Grouper release is v4.x.x non-enhancement version

Read the Release Notes for Grouper v4

Past Grouper release is v2.5.x non-enhancement version

Read the Release Notes for Grouper 2.5

Which version should be used

Use versionIn these conditions
v5.*.*You want new Grouper features as they are released
You have non trivial testing process on upgrades
Upgrade to latest stable v5.*.* at least every quarter
Upgrade to latest stable v5.*.* when security advisories are released
Use ABAC

v4.*.*

(was 2.6)

You want as little change/risk as possible when upgrading containers
(for OS / security / critical bug fixes)
You do not want to test thoroughly when upgrading
Upgrade to latest stable v2.6.* at least every quarter
Upgrade to latest stable v2.6.* when security advisories are released
Using the Grouper Provisioning Framework
v2.5.*You want as little change/risk as possible when upgrading containers
(for OS / security / critical bug fixes)
You do not want to test thoroughly when upgrading
Upgrade to latest stable v4.*.* by May 2023
v2.4.*Do not use
v2.3.*Do not use
v2.2.*

Do not use

v2.1 or earlierSeriously?

Release components

Grouper in v4 is a container.  If your institution does not run containers regularly, it's ok, you can run Grouper without making investments in container orchestration.

For the Grouper container, which runs the Grouper UI, WS, daemon, scim, GSH, see:


New Features in Grouper 2.5

 Grouper 2.5 includes many helpful new features, as listed below, as well as the enhancements provided in Grouper 2.4 patches, such as visualization and reporting

The upgrade from 2.4.0 to 2.5 is not generally a major upgrade.  The database did not change much. 

You are required to use a container when running Grouper. This will ensure you have consistent directory structure, the correct version of libraries, and low risk and low effort upgrades.  There are instructions to make using the container as easy as possible.


Grouper source code
is on GitHub.

Previous Grouper Versions

For previous Grouper versions, click the link for the desired version:

2.4.0: 2.4.0 
2.3.0: 2.3.0
2.2.2: 2.2.2
2.2.1: 2.2.1
2.2.0: 2.2.0
2.1: 2.1.52.1.4, 2.1.3, 2.1.2, 2.1.1, 2.1.0
2.0: 2.0.3, 2.0.2, 2.0.1, 2.0.0
1.7: 1.7.0
1.6: 1.6.3, 1.6.2, 1.6.1, 1.6.0

Grouper Email Subscriptions

Please see this page for info on the Grouper email lists and InCommon-Grouper slack.


License

Grouper is licensed under the Apache 2.0 license. See http://www.apache.org/licenses/LICENSE-2.0.html for a copy of this license.

Development of this software was supported with funding from Internet2, the University of Chicago, University of Pennsylvania, Duke University, University of Washington, University of Memphis, University of Bristol (UK), the NSF Middleware Initiative (NSF 02-028, Grant No. OCI-0330626,  Grant No. OCI-0330626, OCI-0721896, and OCI-1032468), and JISC. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF).

  • No labels