Upgrade 3.2 to 3.4.1

wwalker · October 21, 2020, 8:37pm

I installed PrivacyIDEA 3.2 from repositories on ubuntu 18.04. I read the documentation that states I can run apt-get dist-upgrade to perform the upgrade. Is there anything I need to be aware of or additional configurations that I need to make? I’ve heavily modified the UI through the use of Apache rewrites, will I need to reconfigure privacyidea.conf under sites-enabled? We also utilize the freeradius integration, anything to be aware of from that aspect?

plettich · October 23, 2020, 9:38am

Usually all changes that might affect an update are noted here:

github.com

privacyidea/privacyidea/blob/branch-3.4/READ_BEFORE_UPDATE.md

# Update Notes

## Update from 3.3 to 3.4

* Policies can now contain the privacyIDEA node as condition.

  Be sure to run the schema updates in you pip installation.
  Ubuntu or CentOS installations will run the schema update automatically.

* The SMS Gateway database tables have been enhanced with an additional
  constraint on the type of the options.

  The data in the column "Type" of the database table "smsgatewayoption"
  will be migrated by the schema update script.
  If you are using SMS Gateways, check your gateway configurtion
  after the update.

## Update from 3.2 to 3.3

* Admin policies now do have a destinct admin username field.

This file has been truncated. show original

The update via apt should not touch a modified privacyidea.conf (and there shouldn’t be any changes anyway).

wwalker · October 23, 2020, 6:55pm

Guess I forgot to hit the submit button the other day when I completed my upgrade.

I am post-upgrade and the upgrade process did really well. All the primary functions still work, token authentications within the GUI and token authentication via freeradius are testing successful.

The only areas I have run into minor issues is with the GUI.

Apache sites-enabled config file was completely overwritten, had to restore from a backup. Actually, I just modified the new one referencing the backup. I didn’t want to overwrite a new setting. Technically this is a bit more than minor as it manages the web server configuration and I’ve got some extra hardening configurations here. Getting back to my configured state was only a couple minutes though.
favicon and title reverted to defaults. This was expected as I couldn’t get an apache rewrite rule for header.html
Added Dashboard menu item to custom menu.html
A couple minor CSS changes to get the UI to properly align again.