...
Date | Upgrading from version | Upgrading to Version | Note for version | Importance | Step needed if... | Description | Jira | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2020/10/20 | All | v2.5+ | 2.5.36 | Not important | If you want to make sure inherited privs get converted correctly | Either run the Upgrade Task daemon or let it run, then query for inherited privilege rules that arent owned by GrouperSystem, there should be none. Use the application template, after that still should be none.
| ||||||||
2020/10/20 | ALL | v2.5.* | 2.5.36 | Medium important | If your IdP timeout is not 10 hours | The default tomee session timeout is now 10 hours instead of 30 minutes in the UI. And 1 minute instead of 30 minutes in the WS. Change this default in your UI to your IdP SSO length with container env var: GROUPER_TOMCAT_SESSION_TIMEOUT_MINUTES | ||||||||
2020/10/20 | All | v2.5.* | 2.5.36 | Important | If you use Grouper | Look at the startup logs for the container to make sure there are no errors, and make sure file customizations still work | ||||||||
Date | Upgrading from version | Upgrading to Version | Note for version | Importance | Step needed if... | Description | Jira | |||||||
2020/09/16 | All | v2.5.* | 2.5.35 | Important | If you use Grouper | DDL updates | 2020/09/16 | v2.4+ | v2.5.* | 2.5.35 | Medium important | If you have configuration in the database | You will not see history for existing DB configs until you run the SQL in your DB, see jira | |
2020/07/21 | All | v2.5.33 | 2.5.33 | Important | If you use Grouper | DDL updates | ||||||||
2020/07/21 | v2.5.25+ | v2.5.* | 2.5.33 | Probably not important | If you have a recent membership group configured | After upgrade, run the "Upgrade Tasks" daemon, or wait an hour. If you have used "recent memberships" you will see the attributes moved from the source group to the target group. | ||||||||
2020/07/21 | All | v2.5.* | 2.5.33 | Important | If you use LDAP and are interested in pool validation | This defaults to validate connections periodically instead of on checkout for performance reasons. See Jira for details. The default is now to check pool every 30 minutes, you probably want to set something lower. | ||||||||
2020/07/21 | v2.5.* | v2.5.* | 2.5.33 | Not important | If you are expecting apache indexes to be on (previous default) | Set the container env var to get previous behavior: GROUPER_APACHE_DIRECTORY_INDEXES=true | ||||||||
2020/07/21 | All | v2.5.* | 2.5.33 | Might be important | If you are putting configs in the DB and want to import externalized text config to DB: grouper.text.en.us.properties | Import that file to the DB and remove from container overlay or mount | ||||||||
2020/07/21 | All | v2.5.* | 2.5.33 | Important | If you overlay the server.xml and not use ENV vars to configure | You need to make sure the ajp connector will work: secretRequired="false" address="0.0.0.0" allowedRequestAttributesPattern=".*" | ||||||||
2020/07/21 | v2.5.25+ | v2.5.* | 2.5.33 | Important | If your loader query or group_loader query in the group: etc:attribute:recentMemberships:grouperRecentMembershipsLoader is not a simple select from a view | Delete that group, restart grouper (any service), see the group recreated with the correct query. Make sure it is scheduled and run the loader job once. | ||||||||
2020/05/13 | v2.5.* | v2.5.* | 2.5.29 | Not important | If you care about the log prefix of logs or need to revert to old behavior | -e GROUPER_LOG_PREFIX=grouper Log prefix. By default it is "grouper-ui' for ui-only container. grouper-ws for ws-only. grouper-scim for scim-only. grouper-daemon for daemon-only. Or "grouper" if not set to something else. | ||||||||
2020/05/13 | v2.5.* | v2.5.* | 2.5.29 | Not important | If you use any of these env vars in your Dockerfile or container: RUN_APACHE, RUN_SHIB_SP, RUN_TOMEE, RUN_HSQLDB, SELF_SIGNED_CERT | Add prefix GROUPER_ to them | GRP-2776 | |||||||
2020/05/13 | v2.5.* | v2.5.* | 2.5.29 | Important | If you are overlaying or replacing text in files that can use new env vars, use those | Review v2.5.28 changes on container documentation page. | NA | |||||||
Date | Upgrading from version | Upgrading to Version | Note for version | Importance | Step needed if... | Description | Jira | |||||||
2020/05/05 | v2.5.* | v2.5.35 | v2.5.27 | Important | If you overlay the grouper.xml or grouper-www.conf, and not from the shell hook method | You should patch these files correctly from the shell script hook | ||||||||
2020/05/05 | All | v2.5.* | v2.5.27 | Important | If you use GSH scripts | If you have cron'ed GSH scripts or run GSH script manually, the error handling changed, which might affect how these complete. See Jira | GRP-2732 | |||||||
2020/05/05 | All | v2.5.* | v2.5.27 | Not important | If you have usdu or badMembership in your grouper-loader.properties config | Some jobs were split out to have single purpose daemons, see Jira for details | ||||||||
2020/05/05 | All | v2.5.* | v2.5.27 | Not important | If you use WS or UI diagnostics URL (/status) and do not want group names in diagnostics output | You can report an abbreviated list for diagnostics if you like | ||||||||
2020/05/05 | v2.4+ (container) | v2.5.* | v2.5.27 | Important | If you use /opt/grouper/lib directory in container | We used to copy this directory to /opt/grouper/grouperWebapp/WEB-INF/lib, but no longer. Mount or copy to the right place. See Jira for details. | ||||||||
2020/05/05 | v2.5.25+ | v2.5.* | v2.5.27 | Not important | If you dont want a temporary diagnostics error | You might want to run the recent memberships loader job manually after upgrading so you don't get diagnostics errors of a daemon that hasn't run | ||||||||
2020/04/21 | All | v2.5.* | v2.5.23 | Probably not important | If you have dbUrl in subject.properties | Database connections in grouper are configured in grouper-loader.properties, move it there. See Jira for details | ||||||||
2020/04/21 | All | v2.5.* | v2.5.23 | Probably not important | If you use vt-ldap | If you know that you use the vt-ldap interface, or if you search your configs for "vt", follow the instructions in the Jira. Only ldaptive is supported now. | ||||||||
2020/04/21 | All | v2.5.* | v2.5.23 | Important | If you have morph string secret configured in external file from morphString.properties encrypt.key = /some/path/morph.secret | Carefully inspect your morphString.properties and see if there is a newline in your secret file path: /some/path/morph.secret If so, then set this in morphString.properties encrypt.trimWhitespaceFromMorphSecretFile = false | ||||||||
2020/04/21 | All | v2.5.* | v2.5.23 | Not important | If you configured the workflow schedule | Search for "workfow" in grouper-loader.properties, change to "workflow" | ||||||||
2020/04/21 | All | v2.5.* | v2.5.23 | Not important | If you use grouper jars outside of container | You can remove base properties files in classpath | ||||||||
2020/04/08 | v2.4 | v2.5.* | v2.5.22 | Upgrade instructions from v2.4 to v2.5 |
...