Crowd 2.7 Release Notes

23rd September 2013

The Atlassian Crowd team is pleased to bring you Crowd 2.7 with a breadth of exciting new features and improvements!

Common administrative tasks can now be carried out more efficiently, particularly in large enterprise deployments. This will enable Crowd administrators to save time so they can get more done.

We recommend you read the upgrade notes for important information about this release.

 

Thank you for your feedback:

(green star) More than 200 votes satisfied

(green star) Over 40 features and improvements requests fulfilled

 

Highlights of this release:

 

User rename

Users in Internal Directories can be renamed by simply editing their username in the UI:

Moreover, if a user is renamed in your LDAP directory, Crowd will pick that up in the next synchronization of a Connector directory, or when the user authenticates against a cached Connector or Delegated Authentication Directory. All user attributes and memberships are carried over when the user is renamed.

Scheduled backups

You backup Crowd regularly, don't you? We have now made this easier than ever by providing you with the ability to schedule daily backups, at a time that's convenient for your team. Crowd will back up its directories and configuration, and automatically rotate old backup files. If you are upgrading from a previous version of Crowd, you will need to enable scheduled backups in the Administration section.

Improved Microsoft Active Directory integration

We know that many of you integrate Crowd with Microsoft Active Directory. We've now made this integration more powerful in two ways:

Support for Active Directory primary group memberships

Users' primary group memberships in Active Directory are now visible to Crowd. This means that you can now grant users access to applications in Crowd based on their primary group.

Support for disabled users in Active Directory

Users who are now disabled in Active Directory will be automatically disabled in Crowd when Crowd next synchronizes. This is a configurable option.

This synchronization goes both ways, so if you disable or enable a user from within Crowd, this will propagate back to Active Directory. You'll be able to manage the user status in all applications with one click and in a single place. Newly configured directories will have disabled users support enabled by default.

If you are upgrading from a previous version of Crowd and would like to would like to enable this feature, you will need to un-tick the "Manage user status locally" option in the directory configuration.

If you do not have read/write access to your Active Directory server, you can disable this support by selecting the option to manage user status locally. This simply reverts to the former behavior where the status is not synchronized and you continue to manage it locally in Crowd.

Simpler setup

You can now get Crowd up and running faster than before. We've streamlined the setup wizard so that only the minimum requirements must be configured. If you are evaluating the product, you can choose to accept the defaults supplied and make further configurations at a later stage.

Complete list of improvements and fixes

キー 要約 P ステータス
Loading...
Refresh

 

 

最終更新日 2016 年 5 月 26 日

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

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