Crowd 2.8 Release Notes

10th November 2014

The Atlassian Crowd team is pleased to bring you Crowd 2.8 with a thorough UI refresh, more control over groups with multiple directories, and many other features and fixes.

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

Thank you for your feedback:

(green star) More than 45 votes satisfied

(green star) Over 30 feature and improvement requests fulfilled

Highlights of this release:

 

A full user interface makeover using the Atlassian Design Guidelines

Crowd's interface got a makeover using the Atlassian Design Guidelines:

Direct access to administration:

Workflow steps are indicated up front:

Choose whether or not to merge group memberships from multiple directories

One of Crowd's most voted feature requests (Add option that would allow group memberships to be aggregated across directories again), you can now choose to aggregate group memberships for a user defined in multiple directories.

Read more about aggregating group memberships...

A new experimental lightweight OpenID server

Following on from the OpenID approval whitelist, Crowd now has a new lightweight UI-free OpenID server that uses persistent identifiers unaffected by renaming. It's located at /openidserver/v2/op, and no database setup is necessary.

Read more about the new lightweight OpenID server...

Support and library upgrades

Many other fixes and upgrades including:

  • Spring LDAP 2.0
  • Apache HttpComponents 4.3
  • Support for PostgreSQL 9.3

These changes improve compatibility and introduce caching for integrated applications fetching the current cookie configuration.

Complete list of improvements and fixes

Loading
Key Summary P Status
CWD-3147 If a user exists in two directories in an application, and is added to a group in one directory that it was already in the other, clients get duplicate key errors Medium Resolved
CWD-2135 Add option that would allow group memberships to be aggregated across directories again Medium Resolved
CWD-2942 Replace commons-httpclient with Apache HttpComponents Medium Resolved
CWD-3796 Group amalgamation behaviour is inconsistent in Crowd Medium Resolved
CWD-3195 Update Crowd's UI to the new ADG look & feel Medium Resolved
CWD-3997 Disabled applications still counting under "Current Users" total. Low Resolved
CWD-3961 Disabled user are still able to request for password reset email. Medium Resolved
CWD-3648 As an admin, I want to use the REST API to create users with an already hashed password Low Resolved
CWD-3556 Allow for caching when retrieving cookie configurations (GET /config/cookie method) Low Resolved
CWD-4235 Extend Username field to match Email Address field Low Resolved
CWD-3966 Create API to invalidate all users passwords Low Resolved
CWD-3870 As an admin, I want to choose the membership aggregation semantics I want for each application Low Resolved
CWD-3831 Officially support PostgreSQL 9.3 Low Resolved
CWD-4011 Crowd Rest Client always uses absolute url when revalidating http request Highest Resolved
CWD-4029 Crowd Async client does not handle network errors Highest Resolved
CWD-4055 Crowd doesn't update hibernate's User/Group caches with Attribute changes High Resolved
CWD-3658 Support for sending ADG HTML emails by plugins Medium Resolved
CWD-1499 Crowd console searches should be GET, not POST Medium Resolved
CWD-1173 CSV import fails if a column is unmapped. Medium Resolved
CWD-4001 NPE thrown from com.atlassian.sal.api.user.UserManager.getRemoteUser() Medium Resolved
Showing 20 out of 103 issues Refresh

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport