Preparing for Confluence 7.17
This documentation is intended for Confluence developers who want to ensure that their existing plugins and apps are compatible with Confluence 7.17.
Watch this page to find out when a new milestone is available and what’s changed. We will publish formal release notes once we release a beta.
|14 March 2022
Issues with this milestone?
Hit the Feedback button on the Confluence EAP header or raise an issue to tell us about it.
On this page:
In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your app. We'll indicate when a change has been implemented, and in which milestone.
We're continuing to identify and upgrade core components and libraries to the newest versions. We will not break our official APIs. However, certain libraries, transitive dependencies, and behaviours might change.
Configuring Confluence as an OAuth 2.0 provider
You can now configure Confluence as an OAuth 2.0 client and provider. If you’d like to switch to using OAuth 2.0, you’ll need to update your current integrations that use OAuth 1.0 or build new ones, to be compatible with Confluence. To understand what OAuth 2.0 flows are available and what data you need, see the Confluence OAuth 2.0 provider API.
Invalid license check
If a Confluence Data Center or Server license isn't valid, system administrators will now see a banner prompting them to contact their license issuer to confirm.
New metrics for monitoring apps
We now expose a series of metrics to help diagnose performance issues with bundled and installed apps. The metrics monitor things like time spent on reindexing, SAL transactions, or web resource conditions. You can also create your own metrics for your apps.
Status: ADVANCE NOTICE
We're working on upgrading Hibernate from 5.2 to 5.4. This includes breaking changes like removing deprecated features/interfaces.
Notable features that have been removed:
- Support for JDBC parameterised queries. Classes that implement
HibernateContentQueryFactoryshould be verified to assure that named parameters are used instead.
RegionAccessStrategyand other access strategy interfaces have been replaced.
See Hibernate 5.2 to 5.4 upgrade contains breaking changes for more information.
We are now targeting our next platform release (8.0) for this work.
Removal of editor-v3
Status: ADVANCE NOTICE
When we upgraded our editor to TinyMCE v4 way back in Confluence 6.14, we introduced an unsupported dark feature that could be used to revert to the v3 editor (
frontend.editor.v4.disable). We plan to remove this dark feature flag in a future Confluence release, as they are no longer tested or reliable.
Once that happens, the
editor-v3 WRM context will no longer be loaded. Any resources used only in this context can be removed completely. The
editor-v4 contexts are unchanged, and with this change, resources in
editor-v4 can be safely moved to
In this section we'll provide details of changes we have implemented, organised by the milestone they are first available in. This will help you decide which milestone to use when testing.
Release candidate - 14 March 2022
No significant changes in this release candidate.
Beta 1 - 2 March 2022
In this beta release:
Make your integrations more secure with OAuth 2.0
- New monitoring for installed apps
- Encrypt database password
- Support for PostgreSQL 12, 13, and 14
See Confluence 7.17 beta release notes for full details of everything in this release.
EAP 3 – 21 February 2022
- Added support for PostgreSQL 12, 13, and 14
- Upgraded confluence-compat-lib to 1.4.2 to resolve a problem with the xstream-security module not working in developer mode (see - CONFSERVER-74692Getting issue details... STATUS )
EAP 2 – 16 February 2022
- No significant changes in this milestone.
EAP 1 – 7 February 2022
- Application links updated to support OAuth 2.0 for linking to external applications.