Confluence 7.16 Upgrade Notes

Here are some important notes on upgrading to Confluence 7.16. For details of the new features and improvements in this release, see the Confluence 7.16 Release Notes

On this page:

Upgrade notes 

Considerations when disabling basic authentication

As mentioned in the release notes, you can now configure multiple identity providers for authentication, and disable username and password authentication, also known as basic authentication, which is a less secure form of authentication. 

There are a few things to be aware of before you disable username and password authentication:

  • User signup up is only available with username and password authentication. Users will not be able to create themselves an account if you disable this authentication method. If you have multiple methods available, users will need to select the 'Continue with username and password' option on the login screen to see the sign up option. 

  • Any existing scripts or integrations that rely on the API should be updated to use personal access tokens, otherwise they will stop working when you disable username and password authentication. 

Change to page and attachment version numbering

As part of our work to introduce retention rules for historical page and attachment versions, we have changed the way versions are numbered in the page history and attachment history in Confluence Data Center.

Versions will no longer be renumbered when deleted by a user, or by the retention rules scheduled jobs. This may cause issues for any custom apps or integrations that rely on the current behaviour where versions are renumbered after deletion.

See an example...

In this example version 6 was deleted manually by a user (1), and versions 3 and earlier (2) were deleted because they didn't meet the retention rule criteria. 

Database requirements for faster permissions service 

  • If you use SQL Server, your database user needs full create, read and write permissions for the database tables. Confluence must be able to create its own schema, and have the ability to create/drop triggers and functions. Refer to your SQL Server documentation for how to do this. 

  • If you use Oracle, you must use Oracle 12c Release 2, there are known problems with Release 1 (which is no longer supported by Confluence). 

Change to bullet point appearance

We've fixed a long standing issue with the appearance of bullet points in indented lists. This means the appearance of your existing lists will change, including macros that use bullets to display content, such as the Table of Contents macro and Children display macro.


Supported platform changes

Added support for Microsoft SQL Server 2019. 

End of support announcements

Advance Notice: End of support for selected databases

  • Confluence 7.16.x will be the last release to support Microsoft SQL Server 2016
  • Confluence 7.17.x will be the last release to support PostgreSQL 10

For more information on these notices, see End of Support Announcements for Confluence

Infrastructure changes 

Head to Preparing for Confluence 7.16 to find out more about changes under the hood. 

Known issues

If you encounter a problem during the upgrade and can't solve it, please create a support ticket and one of our support engineers will help you.

Upgrade procedure

Always test the upgrade in a test environment before upgrading in production.

To upgrade Confluence to the latest version:

  1. Go to  > General Configuration > Plan your upgrade and select the version you want to upgrade to. This will run the pre-upgrade checks.
  2. Go to  > General Configuration > Troubleshooting and support tools to check your license validity, application server, database setup and more.
  3. If your version of Confluence is more than one version behind, read the release notes and upgrade guides  for all releases between your version and the latest version.
  4. Back up your installation directory, home directory and database.
  5. Download the latest version of Confluence.
  6. Follow the instructions in the Upgrade Guide.

Update configuration files after upgrading

The contents of configuration files such as server.xml, web.xml , setenv.bat / setenv.sh and confluenceinit.properties change from time to time. 

When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation, otherwise you will miss out on any improvements we have made.

Last modified on May 3, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.