Confluence 7.2 ベータ版リリース ノート

Atlassian presents Confluence 7.2.0-rc1. This is a snapshot of our work in progress, primarily focused on providing app developers an opportunity to test their apps and make any required changes in advance of an official release.

Confluence 7.2.0-rc1 は今すぐダウンロードできます

Development releases are not production ready. Development releases are snapshots of the ongoing Confluence development process. While we try to keep these releases stable, they have not undergone the same degree of testing as a full release, and could contain features that are incomplete or may change or be removed before the next full release.

No upgrade path. Because development releases represent work in progress, we cannot provide a supported upgrade path between development releases, or from any development release to a final release. You may not be able to migrate any data you store in a Confluence development release to a future Confluence release.

Atlassian does not provide support for development releases.



Highlights of 7.2.0-rc2

2019 年 12 月 6 日にリリース

このリリース候補には、RC1 で見つかったいくつかの問題の修正が含まれています。  

Highlights of 7.2.0-rc1

2019 年 12 月 4 日にリリース


Highlights of 7.2.0-beta1

2019 年 11 月 27 日にリリース

現在のインフラストラクチャで Data Center 機能にアクセス

Data Center 製品は当初、エンタープライズ企業がアプリケーションのアップタイムを増加させ、大規模環境でパフォーマンスを維持することを支援するため、クラスタ環境向けに設計されていました。

Since then, we've shipped a suite of additional features designed to give admins more flexibility and control: SAML single sign on, read-only mode for site maintenance, and CDN support.

Now, you can access all of these features on your current Server infrastructure simply by applying a Data Center license. Clustering is still available and ready to enable when you want to scale, but it’s no longer required as part of the license upgrade.

Learn more about the full set of features available with a Data Center license.

アップグレード ノート

Using Companion app in single sign-on environments

If you've configured single sign-on (SSO) in such a way that your reverse proxy redirects the requests to your SSO gateway, and only successfully authenticated requests ever reach Confluence, your users won't have been able to use Atlassian Companion app. This is because the Atlassian Companion app uses JWT tokens to authenticate requests, and only Confluence can authenticate these requests, not your SSO authenticator. 

To make sure requests from the Atlassian Companion app can be authenticated, you can now configure your reverse proxy to always allow requests from the following URLs: 

  • <base-url>/rest/token-auth/api/* 
  • <base-url>/download/token-auth/attachments/*
  • <base-url>/plugins/servlet/imgFilter*  
  • <base-url>/rest/analytics/1.0/publish/bulk   (only necessary if you have opted in to data collection)

If an unauthenticated user tries to access these URLs directly, they would be redirected to the Confluence login screen. They wouldn't be able to access any content or download files while unauthenticated.

Chart macro maximum size

We now limit the maximum height and width of the Chart macro. This will help avoid performance problems if a user accidentally enters a very large value, as we'll automatically resize the chart to 3000px by 3000px. You can modify the default maximum using the  following system properties:

  • confluence.chart.macro.width.max  
  • confluence.chart.macro.height.max 

Minor change to Lucene implementation

We've made a change to the implementation of the term filter. A bitset is now only created when the number of matches is large enough to benefit from it. This helps reducing unnecessary CPU and memory usage and avoid bottlenecks. The threshold can be changed via the system property, but we don't expect you should need to do this. 



Confluence 7.2 contains changes that may affect apps. Head to Preparing for Confluence 7.2 to find out how these changes will impact app developers. 

最終更新日: 2019 年 12 月 6 日


Powered by Confluence and Scroll Viewport.