Crowd 7.0 Upgrade Notes

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

21 August, 2025

Here are some important notes on upgrading to Crowd 7.0. To learn about new features, check out the release notes.

 アップグレード ノート

Here's some important information you should know about:tes

Removed support for Freemarker templates

We’re removing support for Freemarker templates. We recommend migration to a safer alternative, such as Soy or Apache Velocity templates.

Migration to new authentication API

We’re deprecating com.atlassian.crowd.manager.authentication.TokenAuthenticationManager. As a more secure alternative, use com.atlassian.crowd.service.authentication.CrowdApplicationAuthenticationService to authenticate and log out users to Crowd.

Other functionalities provided by TokenAuthenticationManager won’t be available in Crowd’s public API.

Removed support for Google Apps connector

Starting from Crowd 7.0, the Google Apps connector functionality is blocked by default. To permanently remove the Google Apps connector if your instance has one configured:

  1. Log in to Crowd.

  2. Go to the Applications tab.

  3. Select Google Apps.

  4. Select Remove application and confirm removal.

More about Google Apps connector

Deprecating user and group attribute sync

We're deprecating the ability to synchronize user and group attributes from external directories. This was an undocumented feature that synchronized user and group attributes with a specific prefix from an external directory. By default, this functionality was disabled and could only be activated by manually editing the directory attributes.

Removal of insecure and deprecated components

We’ve updated and migrated the insecure external components com.sun.activation and com.sun.mail from com.sun to org.eclipse.angus.

We’ve also removed the below components which have been deprecated in the past:

コンポーネント

削除済

Crowd Core

Class: com.atlassian.crowd.embedded.propertyset.DateFormats

Public static methods and fields in:

  • com.atlassian.crowd.embedded.api.Directories

  • com.atlassian.crowd.model.application.Applications

  • com.atlassian.crowd.model.user.Users

  • com.atlassian.crowd.model.group.Groups

Class: com.atlassian.crowd.embedded.directory.LdapConnectionPoolInitialisationListener

Class: com.atlassian.crowd.directory.query.MicrosoftGraphQueryParams

Crowd API

com.atlassian.crowd.embedded.api.AttributesSynchronisableDirectoryProperties:

  • CURRENT_START_SYNC_TIME

  • LAST_START_SYNC_TIME

  • LAST_SYNC_DURATION_MS

  • IS_SYNCHRONISING

Public methods:

  • com.atlassian.crowd.integration.http.CrowdHttpAuthenticator#isAuthenticated

  • com.atlassian.crowd.integration.http.CrowdHttpAuthenticator#rememberMeLoginToCrowd

  • com.atlassian.crowd.service.CrowdRememberMeService#createCookie

Move from jTDS to Microsoft JDBC driver for SQL Server

We’ve removed support for the jTDS driver, and it’s no longer bundled with Crowd. Crowd now supports the Microsoft JDBC Driver for SQL Server, ensuring ongoing compatibility with SQL Server databases. Either you want to continue using the JTDS driver (not recommended) or move to the MS JDBC driver (recommended), you’ll have to add the driver manually to tomcat/lib directory. Explore how to set up Crowd with MS SQL Server database

If you're upgrading an existing instance to Crowd 7.0, refer to the Transitioning from JTSD to Microsofts JDBC driver article.

アプリのインストール時におけるアプリ署名の既定での有効化

In this release, app signing is enabled by default. This feature improves app security and was gradually rolled out across Data Center products. For details, check out this community post.

アプリ署名は新規アプリのインストールのみに影響し、すでにインストール済みのアプリはそのままです。

必要な手順は、アプリを Marketplace からインストールするか、カスタム アプリを構築するかによって異なります。

Marketplace からアプリをインストールする

この操作を行うには、次の手順を実行します。

  1. Configure the location of the truststore folder as described in Configuring UPM app signature check.

  2. Download and install the Atlassian Certificates bundle. For details, see Updating Atlassian Certificate Bundles.

  3. 以上で完了です。Marketplace から安全にアプリをインストールできます。

カスタム アプリのインストール

カスタム アプリのビルドを使用する場合は、次の手順でご自身のアプリに署名してそれらを保護できます。

  1. Configure the location of the truststore folder as described in Configuring UPM app signature check.

  2. Get the app signature and verification certificate as described in Generating app signature and verification certificate using OpenSSL.

  3. Put your new certificate in your Trust store as described in Updating Atlassian Certificate Bundles.

  4. 署名したアプリをインストールします。

アプリ署名機能を使用せずに、ファイル システム経由でアプリをインストールすることもできます。

If you’re experiencing issues, check out app signing troubleshooting.

 サポート対象プラットフォーム

  • We’re adding support for:
    • PostgreSQL 17
    • MySQL 8.4
    • Oracle 23ai
    • Oracle 19
  • We’re removing support for:
    • Java 17
    • Oracle 12
    • PostgreSQL 10
    • PostgreSQL 11
    • PostgreSQL 12
    • PostgreSQL 13
    • PostgreSQL 14
    • MySQL 5.7
    • MySQL 8.0 LTS
    • SQL Server 2016
    • SQL Server 2017

アプリ開発者向けの情報

See Preparing for Crowd 7.0 for any important changes regarding apps.


最終更新日 2025 年 8 月 21 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.