Grouper Product Roadmap

Grouper Product Roadmap

Grouper Product Roadmap

This roadmap sketches substantial and signal functional enhancements to Grouper, and to align at least some of them with future releases. It is (always!) a work in progress, subject to the considerations and requirements of participants in the Grouper Working Group. It is also a proposition: it represents the default plan that the Grouper core developers will attempt to implement.
Items that have fallen off of the roadmap appear further below with some explanation as to why.

Grouper Version Support

Grouper developers offer support to the versions released in the last 3 months or the latest version in the active major versions (currently v6, v7). 

 

See Grouper Versioning and Support info here.

Release

Tentative date or time frame

Support

Notes

v1.6

Released June 2010

None

 

v2.0

Released September 2011

None

 

v2.1

Released March 2012

None

 

v2.2

Released July 2014

None

 

v2.3

Released April 2016

None

 

v2.4

Released August 2018

None

 

v2.5

Released April 2020

None

 

v2.6

Released September 2021

None

Has both new provisioning and subject sources as well as old

v4

Released March 2023

Stable release

Is same as v2.6, but using semantic versioning

v5

Released October 2023

Stable release

Will only have new provisioners

6.0

Released February 2026

Stable release

Stable version of v5

These are gone in v6 Apache, shib SP WS SOAP Non-provisioning-framework provisioners googleapps-google-provisioner grouperAtlassianConnector grouper-aws-changelog grouper-azure grouper-box grouper-duo grouperKimConnector grouper-pspng grouper-remedy grouper-remedyDigitalMarketplace grouperScim grouper-shib grouper-tierApiAuthz grouper-tier-scim grouper-installer These will still be in Grouper going forward All provisioning framework connectors Custom change log consumers Messaging connectors grouper-messaging-activemq grouper-messaging-aws grouper-messaging-rabbitmq

v7

Released March 2026

Stable release

Grouper OAuth 2.1 authorization server and MCP server

AI assistant in the UI

Compiled Java GSH templates

Work on migrating away from legacy provisioners, SOAP, and Apache in v4.

 

Release

Item

Description

Release

Item

Description

v7

Provisioning activity and auditing

Write audits to the provisioning audit table and read that from UI.  Errors to audit table too?

v7

External system documentation in wizard

For each external system document the specifics in the wizard

v9

Remove legacy subject source configs

Only new subject source available

v7

Add bulk operations

Make bulk operations faster, e.g. creating or deleting a list of groups, adding or removing a list of memberships.  Add bulk hooks

v9

Redesign Grouper DDL

Reduce size, improve efficiency, move to single purpose tables/structure.  Simple integer foreign keys (sequence or auto increment).  Simple integer enums.  Compact core tables with external auxiliary tables.

v7

Performance diagnostics

Administrative function to measure and diagnose the performance of a deployment

v7

Cache redesign

Analyze and improve how Grouper caches objects in and out of Hibernate.  Simply the subject API

v7

Remove Voot

Remove the Voot provisioner

v7

Upgrade Groovy

Major version upgrade of Groovy, for new features

v7

Reorganize Git source

Reorganize Git source directories to be more standard (GRP-5134)

v9

Revisit Grouper service registry

Identify services in grouper.  Make them easy to see, join, manage, document, attest, etc.
https://docs.google.com/document/d/1zV2kuAKOwoBFIf4GIpiQt6-NFsVkdbYdagDjGcJ7efQ/edit

v9

Re-write Grouper WS

Either use SCIM or more targeted REST/JSON to streamline operations.  Proxy from old to new so legacy clients are supported.  New operations will not have SOAP or XML.  SOAP jars will no longer be in Grouper (proxy to another shim project)

?

GSH loader

Allow a loader to be a GSH script to load groups and memberships (like SQL)

?

Migrate Grouper git

For consistency, reporting, licensing reasons, Internet2 would like the Grouper git repo to be in its enterprise account instead of public git