Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Upgrade process from Grouper 2.2.2 to 2.5

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Upgrade process from Grouper 2.2.2 to 2.5

Chronological Thread 
  • From: Scott Koranda <>
  • To: Robert Bradley <>
  • Cc:
  • Subject: Re: [grouper-users] Upgrade process from Grouper 2.2.2 to 2.5
  • Date: Thu, 30 Apr 2020 07:16:23 -0500


I have not upgraded from 2.2.x to 2.5.x, but I did just successfully
complete an upgrade from 2.3.x to 2.5.x.

The strategy I used was to begin by fully patching 2.3.x. I then did an
"in place" upgrade to 2.4.x using the grouperInstaller.jar. Once I was
running a fully patched 2.4.x I then converted from using a subject
sources.xml file to a file and make sure my 2.4.x
still worked. Next I converted to using the database to store
configuration, so that the only remaining configuration in files is and At that point
transitioning to running the 2.5.x container was straightforward.

There were a few issues to watch out for during the conversion:

- I found it worked better to "fix" any collation/character set issues
before the upgrade process began. The 2.3.x deployment was not using
character set utf8 and collation utfb_bin (this is a MySQL/Maria DB
deployment) so I made those changes first.

- I found that after upgrading the core I needed to be careful during
the UI and WS upgrades to make sure I did not ask the installer to
schema check the database. While it seems that the schema
check/upgrade process should be idempotent, I ran into unexplained
errors. The process was smooth when I just did that initially with the
core and then was careful to skip it with the UI and WS.

- After the 2.3.x to 2.4.x the UI would not initially work because the
installer created an extra 'grouper' directory in the UI layout under


I had to move the files in that directory up one directory before the
UI would run.

- After the 2.4.x upgrade before you start to upload configuration files
into the database you will probably have to edit
and add the line

grouperUi.configurationEditor.sourceIpAddresses = <your CIDR here>

to give yourself permission to use the configuration editor.

- I found I needed to copy the file from the WS
part of the 2.4.x deployment tree into the UI part of the 2.4.x
deployment tree in order for the configuration editor in the UI to
work. I think this is a known issue and will be fixed in an upcoming

- You can use the grouperInstaller.jar to do the conversion of
sources.xml to

- This deployment used LDAP as a subject source and the details about
that deployment (bind DN, and so on) survived from sources.xml to, but after the upload of into
the database configuration I needed to make some adjustments because
the way an LDAP subject source is configured is different now. You
need to enter the LDAP connection details in in the section "LDAP connections", probably
using the "personLdap" server ID (one of the defaults). Then you need
to go back to and "link" to that configuration.

- I found that I needed to evolve my JDBC connection URL in from the simple


to the more sophisticated


- To just make sure the transition to the container was working I did
not want to bother immediately with the full Shibboleth SP
configuration, so I edited and added = true = true = true

Then I started the container


I broke into the container and did

grouperPasswordSave = new GrouperPasswordSave();

new Authentication().assignUserPassword(grouperPasswordSave);

Then I could use basic auth to login as GrouperSystem and look around
easily to make sure the container appeared to be working and the 2.5.x
upgraded worked.

- After running the container I wanted to be sure that the schema was
fully upgraded so I broke into the container and ran

./bin/ -registry -check -deep

Not all of the output from that command goes to the stdout of the
shell you are running after you break in, so you need to also look
at the stdout of the container for the "success" message that your
schema is up-to-date (or not). Chris Hyzer is aware and has already
patched that I think...


Scott K

> > Looking at the release notes for Grouper 2.5, I noticed that there
> > are no instructions for upgrading from pre-2.4 versions. As we're
> > currently running version 2.2.2, we are considering upgrading at
> > some point in the near future, and so I was wondering what the
> > correct process would be. Is it possible to jump straight from 2.2
> > to 2.5, or would we need to upgrade via Grouper 2.3 and 2.4 first?
> >
> Has anyone else tried upgrading 2.2.2 to 2.5 yet?

Archive powered by MHonArc 2.6.19.

Top of Page