Meelogic Atlassian Blog

Crowd 4.1 release notes

✓ Support for local groups in Azure Active Directory

✓ UI and UX improvements

✓ New supported environments

✓ Performance improvements

 

 

Support for local groups in Azure Active Directory

Atlassian is introducing support for local groups in Azure AD directories. From now on, you can add groups to Azure AD locally and manage user memberships in it. Local groups won’t be saved in the Azure AD directory. Groups synchronized from the Azure AD directory will remain read-only.

To enable local groups for your directory go to you Azure AD directory settings in Crowd and select Manage groups locally. 

UI and UX improvements

Crowd 4.1 brings you some UI and UX improvements to make your user experience even better.

  • In the Directories tab, a column with the last synchronization status has been added to directories overview. Now you can see at a glance for which directories synchronization succeeded, failed, or is running without having to go to individual directories.

  • In the User tab, you can now search for users in all directories and not only in a selected directory.
  • The look and feel of Applications tab and Groups tab has been modified to make these tab more in sync with the rest of Crowd.

New supported environments

Introducing support for the following databases:

  • Oracle 12c R2
  • Oracle 19c
  • PostgreSQL 10
  • PostgreSQL 11
  • MySQL 8

Introducing support for new browsers:

  • Microsoft Edge (Legacy)
  • Microsoft Edge (Chromium)

For the full list of environments supported by Crowd, see Supported Platforms.

Performance improvements

Improved full sync performance of an application with multiple directories. Fetching non-aggregating memberships is now several times faster. Depending on the data size and shape full sync time should decrease by minutes for ~100k users or hours for ~1M users.