Preparing for Confluence 9.1
This documentation is intended for Confluence developers who want to ensure that their existing plugins and apps are compatible with Confluence 9.1.
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.
Latest milestones
25 September 2024 | 9.1.0-rc1 |
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:
Planned changes
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.
This release only supports Data Center licenses. If you have a Server license, check out your options for upgrading.
URL support for languages and special characters
Status: DONE
Users can now open pages and blog posts using a more intuitive URL that includes the space key, page ID, and page title. The new URL format also supports page titles that contain non-Latin or special characters. References to URLs in the previous format, such as bookmarks, don’t break and instead redirect the user to the new URL.
New URL format example:
https://confluence.example.com/spaces/SPACEKEY/pages/pageId/Page+Title
Two-step verification in Confluence
Status: DONE
To improve the security of the Confluence login experience, we’ve added a second authentication layer.
The new login process supports a built-in two-step verification (2SV) capability using a time-based one-time password (TOTP) generated by an authentication app as a second factor.
If you experience any issues with the new login process during end-to-end build tests or CI/CD of your app, you can switch to the legacy login experience by setting the atlassian.authentication.legacy.mode property to true.
Check out our recent Atlassian developer changelog entry and explore how to manage two-step verification.
Match system as the new default theme and removal of original theme
Status: DONE
We’re updating the default theme in Confluence to ‘match system' so that Confluence follows the user’s preferred theme for their device.
At the same time, we’re also removing original theme, which is visually almost identical to light theme and was kept in Confluence 9.0 for an easy transition.
Removal of custom theme selection from Code Block macro
Status: DONE
As part of our ongoing efforts to streamline and improve the user experience, we have removed the custom theme selection feature. This change simplifies the interface and ensures a more consistent look and feel across Confluence.
Password policy
Status: DONE
Admins can now enforce a stronger password policy for user accounts using an internal directory. This feature aims to prevent users from setting weak passwords and strengthens the overall security posture of the instance.
By default, this setting is turned off by can be enabled by administrator users. Admins have the option to select the recommended password policy, which requires a minimum of 8 characters. Alternatively, they can create a custom password policy that specifies a minimum password length and the number of required uppercase, lowercase, digit, and special characters for password creation.
Preparing for default secrets encryption
Status: DONE
We’re working on providing a default solution for encrypting secrets. This feature will automatically replace the plaintext sensitive values in the database and local or shared home confluence.cfg.xml files with the placeholder {ATL_SECURED}.
The following secrets will now be secured by default:
Database:
Mail server passwords
Calendar passwords
confluence.cfg.xml:
confluence.cluster.authentication.secretconfluence.cluster.aws.access.keyconfluence.cluster.aws.secret.keyopensearch.passwordhibernate.connection.passwordsynchrony.service.authtoken
The values will be encrypted with an AES 256-bit key.
Bundling Java 21 with Confluence
Status: DONE
In this release, we'll bundle Eclipse Temurin Java 21 with Confluence. This version is used when you install or upgrade Confluence with the installer. If you install Confluence manually, you have the option to continue with Java 17 or switch to Java 21.
Check our guide on how to change your Java version
Gadgets coming soon
Status: ADVANCE NOTICE
In Confluence 9.0, we've removed support for gadgets. We’re planning to reintroduce the gadget framework as an Atlassian Marketplace app, making it available for ecosystem usage.
It's important to note that while the gadget functionality will be accessible via the Marketplace, it remains officially deprecated. We strongly recommend that vendors begin migrating to alternative solutions as soon as possible.
Implemented changes
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.
RC 1 – 25 September 2024
Milestone 9.1.0-rc1
Contains:
- Minor bug fixes
Beta 1 – 17 September 2024
Milestone 9.1.0-beta3
Contains:
- Minor bug fixes
EAP 3 – 9 September 2024
Milestone 9.1.0-m85
Contains:
- Minor bug fixes
EAP 2 – 2 September 2024
Milestone 9.1.0-m75
Contains:
Match system as the new default theme and removal of original theme
- Password policy
Preparing for default secrets encryption
- Bundling Java 21 with Confluence
- Minor bug fixes
EAP 1 – 26 August 2024
Milestone 9.1.0-m69
Contains:
URL support for languages and special characters
- Removal of custom theme selection from Code Block macro
- Minor bug fixes
Looking for updated documentation? Check out the Confluence EAP space for the latest docs.
Did you know we’ve got a new developer community? Head to community.developer.atlassian.com/ to check it out! We’ll be posting in the announcements category if when new EAP releases are available.