When upgrading from Grouper v2.6 to another v2.6 container, this wiki will consolidate all the steps needed to perform that upgrade
Note, these are in reverse order, so go from bottom to top
Date | Upgrading from version | Upgrading to Version | Note for version | Importance | Jira | Step needed if... | Description |
---|---|---|---|---|---|---|---|
2022/07/26 | ALL | ALL | 2.6.14 | Important | If you use Grouper | DDL updates - add columns grouper_loader_log.job_message_clob and job_message_bytes | |
2022/07/26 | ALL | ALL | 2.6.14 | Not important | If you use Grouper | csrfguard was upgraded significantly. Click around and import and export and do any UI edge case tasks to make sure the csrf protection does not impede legitimate actions | |
2022/07/26 | ALL | ALL | 2.6.11 | Not important | You use rabbitmq | Check rabbitmq integration, the library was upgraded | |
2022/07/04 | 2.6.6 | ALL | 2.6.10 | Not important | You use OSGI (e.g. the new built in authn) | Add this to grouper.properties in config file or database: # only enable osgi if you use it # {valueType: "boolean", defaultValue: "false", order: 3000} grouper.osgi.enable = true | |
2022/06/07 | ALL | ALL | 2.6.9 | Important | If you use the Grouper provisioning framework | Setup a meeting with someone on the Grouper team to step through upgrading your provisioner | |
2022/05/05 | ALL | ALL | 2.6.9 | Important | If you have SSL anchor certs or client certs in the container | There is a new experimental strategy for this, please see Jiras for details | |
2022/08/06 | ALL | ALL | 2.6.8 | Important | If you use GSH templates have have folderShowType of certainFolder | Change config value from "certainFolder" to "certainFolders" | |
2022/03/02 | ALL | ALL | 2.6.8 | Not important | GRP-3883 | If you use templates and you do not store config in the database, and you use them in 2.6.5, 2.6.6, or 2.6.7 and you have this grouper.properties suffix configured "folderUuidsToShow" | Change "folderUuidsToShow" to "folderUuidToShow" |
2022/03/01 | ALL | ALL | 2.6.8 | Important | GRP-3868 | If you use Grouper | DDL updates - add grouper_prov_duo_user table |
2022/03/01 | ALL | ALL | 2.6.8 | Medium important | GRP-3889 | If you have a SQL provisioner with provisioning framework | Lots of improvements to SQL provisioning. Before upgrade I would export your SQL provisioner config. Then upgrade, and go edit the config, and make sure it looks ok, and save. Then compare the old and new and see if anything changed and adjust that. Run the provisioner and make sure it works. |
2022/02/26 | ALL | ALL | 2.6.7 | Important | GRP-3864 | If you use Grouper | Run the OTHER_JOB_syncAllPitTables daemon |
2022/02/25 | ALL | v2.6.7.1+ | v2.6.7.1 | Medium important | GRP-3860 | If you customize logging with a log4j.properties overlay or additional properties | Either convert to log4j2.xml, or put additional loggers/appenders in /opt/grouper/grouperWebapp/WEB-INF/classes/log4j2.additionalLoggers.xml.txt / log4j2.additionalAppenders.xml.txt <Logger name="edu.a.b.c" level="debug" additivity="false"> <AppenderRef ref="grouper_error"/> </Logger> |
2022/02/18 | ALL | ALL | 2.6.7 | Important | GRP-3832 | If you use Grouper | Run the OTHER_JOB_upgradeTasks daemon, then run the OTHER_JOB_syncAllSetTables daemon |
2022/02/16 | ALL | ALL | 2.6.6 | Important | If you use Grouper | DDL updates | |
-Dlog4j1.compatibility=true | |||||||
2022/01/02 | ALL | ALL | 2.6.6 | Not important | If you care about UI text changes | The term "More" has been changed in the UI to make things less confusing. You can edit your configs to revert Loader moved from "More tab" to "Group actions" menu Group actions menu reorganized | |
2022/01/02 | ALL | ALL | 2.6.6 | Important | If you use Grouper | Folder security has changed. People will only see folders if they have a privilege on the folder or an object in the folder or subfolder. If you don't want this set this in grouper.properties. Note if you set this to true it should probably be temporary until you have worked out the issues. Assign stemView privilege to folders so people see them if they don't see them based on privileges. You could also add power users to a group who can see all folders. # if all folders should be shown only if there is an object inside that the user can see (or a privilege on that folder). # this has been re-coded and is the new setting. The old setting "security.show.folders.where.user.can.see.subobjects" is not used anymore # {valueType: "boolean", required: true} security.folders.are.viewable.by.all = false Remove this config from grouper.properties security.show.folders.where.user.can.see.subobjects | |
2021/10/20 | v2.6.4 | ALL | 2.6.5 | Important | If you use Grouper | DDL updates | |
2021/10/23 | ALL | v2.6.1+ | v2.6.1 | Important | GRP-3670 | If you do not want users to use Grouper built-in self service web service credentials | |
2021/10/21 | ALL | v2.6.3 | v2.6.3 | Not important | GRP-3669 | If you use postgres or oracle, and you areon version v2.6.3 exactly (rare), and these cols are not nullable | |
2021/10/20 | v2.6.0 | ALL | 2.6.1 | Important | If you use Grouper | DDL updates | |
2021/09/22 | ALL | v2.6.* | v2.6.0 | Medium important | You have auto-ddl set in the grouper config | In grouper.hibernate.properties bump up the auto-ddl version registry.auto.ddl.upToVersion = 2.6.* |