Upgrade from previous version

Current version is 2.0 - 3.0.

Even though PhenixID server is fully compliant with previous versions there are differences. Upgrades should not be done without contacting PhenixID.

When contacting PhenixID please add information about current usage of PhenixID server. This will help in assessing the work upgrading the system.

The current version is pre 4.2

Be sure to look through the previous manuals for details.

The current version is 4.2

The installer will guide through the update. Be sure to backup the existing installation before starting the upgrade.

Step by step document for upgrade can be found here:

New version of Hazelcast

New version of Hazelcast is being introduced, with new cluster.xml. This  file needs to be replaced manually in the folder /classes after the  upgrade. Rename earlier cluster.xml and then change cluster_template.xml  to cluster.xml

If cluster is configured, the configuration in the network section must be moved from the earlier cluster.xml to the new one.


As always, verify customizations from earlier version and transfer to new installation if needed.


There has been changes to the "front end files" such as css, js and templates. If you see strange behavior with the web apps or authentication pages, please clear the browser cache.

From version 2.6 there has been a change to the template file used by One Touch.
The server will now look for this file in the folder /resources and the name of the default template file has changed from onetouch_template_json.template to ot_auth_template.json.
If there are One Touch scenarios configured in earlier versions, please go into the Configuration Manager, locate your scenario(s) for One Touch and click on the tab "Advanced".
Edit the name of the template file according to your environment.

If One Touch tokens have been enrolled in version 2.7 and before, you might see this error on startup.

BankID v6.0

In version 4.7 it is possible to upgrade to v6.0 by adding the attribute "version" : "v6.0" to your configuration and removing the use of personalNumber to trigger authentication from your environment. 


If any of these extended valves has been added to your configuration, they must be re-installed after upgrading:

  • GetHsaPersonValve
  • GetMiuForPersonValve
  • MiuMergeDataFromItemsToSessionPropertyValve
  • NavetLookupValve
  • SPARLookupValve
  • BolagsverketEngagemangLookupValve

Please find the installation instructon for each valve in the document article for the valve.