This page last changed on Jun 22, 2007 by justen.stepka@atlassian.com.

The Atlassian Crowd team is proud to announce the release of Crowd 1.1.

This release contains a whole host of new features targeted at implementing OpenID, along with core updates to the Crowd Administration Console.

OpenID-enable your organisation with CrowdID

OpenID enables you to use a centralised identity to login to any website that supports OpenID. It opens up the possibilities of massive scale cross-domain SSO.

Think about all the accounts you have online: blogs, wikis, to-do lists, photo galleries. The list is endless. Even simple tasks such as leaving comments on someone else's blog may require you to register an account with that particular blogging system. This leaves you, as an end user, to set up and manage numerous accounts on each of these sites. With OpenID, rather than managing all these disparate accounts individually, users can manage their identity in one place via an authentication server.

With the ever-increasing adoption of this open authentication framework, including names such as Microsoft, AOL, Sun, Verisign and Firefox, expect to see many applications enabled for OpenID authentication.

CrowdID offers OpenID to an organisation's user base, allowing users to manage their online identity. Everything from configuring different profiles, managing trusted sites to reviewing authentication activity, is accessible from CrowdID. Administrators can set up whitelists/blacklists so that only trusted hosts can request authentication and can set up secure communication via SSL. All of the users can be managed via Crowd's security server, utilizing LDAP services from products such as Microsoft Active Directory.

Included with CrowdID is a sample OpenID client application, providing a working example of an OpenID enabled application. This will help developers kick start OpenID-enabling their applications.

Using OpenID

Rather than registering and typing in your username and password on each site that you visit, OpenID allows you to type a URL similar to 'openid.mycompany.com/users/jstepka':

The OpenID website that you are logging in to will redirect you to CrowdID, which will ask you if you would like to allow authentication with the requesting site.

You can even choose to 'Always' allow authentication with particular OpenID sites, which allows pass-through authentication if you are already logged into your CrowdID server. If you do this, then when you visit the site later, simply provide your URL (e.g. 'openid.mycompany.com/users/jstepka') and you are in.

Think of it as 'Remember Me' for the whole internet!

'Blacklist' and 'Whitelist'

'Blacklists' and 'whitelists' allow administrators to lock down CrowdID their server so that, if necessary, it can only communicate with trusted hosts with which you have established relationships.

A blacklist will prevent specific hosts from communicating with the OpenID server. A whitelist will allow only specific hosts to communicate with the OpenID server.

OpenID Advanced Options

Some external sites implement security better than others. With CrowdID, you can pick how tough you want to be on OpenID sites that communicate with your Crowd OpenID server.

Crowd Console and Server Updates

Choose Your Encryption Type

Every administrator has their own password policies. When using a Crowd Internal Directory you can now select the level of encryption you need.

Import Your JIRA and Confluence Passwords

Migration can be a pain. To ease your switch from existing Atlassian products, Crowd can now import your existing passwords!

Faster Web-Services

Crowd web-services now support GZip compression, improving the performance when downloading large amounts of data such as the all the members of a large group or when performing large search.

Improved Apache and Subversion Integration

The Apache and Subversion library performance has been improved with the implementation of client-side caching of approved authentication requests.

Jive Forums 5.5 Support

The Jive Forums centralised authentication connector has been updated to support the new 5.5 major release of Jive Forums.

LDAP Configuration Tester

When setting up a Crowd LDAP connection you can now verify that your configuration connects as expected.

JIRA Issue Tracker

Atlassian JIRA (50 issues)
Key Summary Pr Status
CWD-376 Export fails when an application does not have a description. Blocker Resolved
CWD-359 'Blacklist' and 'Whitelist' options display intermittently in IE Blocker Resolved
CWD-271 Login and Logoff for OpenID Server application. Blocker Closed
CWD-245 Jive Forums 5.5 Support Blocker Resolved
CWD-379 Change Password link on openid.atlassian.com throws 'No Action' error page Major Resolved
CWD-377 Updating an Application will update the password for an application, even when you do not type in a new password Major Closed
CWD-360 ORA-01000: maximum open cursors exceeded Major Resolved
CWD-354 suggestions for the OpenID login page Major Resolved
CWD-351 When logging out of Bamboo and anonymous mode is turned off, users still have the ability to create plans etc. Major Resolved
CWD-343 Atlassian-user integration - get display name attribute from attributes if there rather than building display name adhoc. Major Resolved
CWD-332 Test configuration buttons when creating an LDAP directory connector. Major Resolved
CWD-323 Test connection utility for LDAP servers. Major Resolved
CWD-320 Improve the importing of users from Confluence and JIRA so these users do not need to reset their passwords Major Resolved
CWD-319 The export function of Crowd needs to have a flag to say don't export domain. Major Resolved
CWD-318 ApacheDS crowd integration does not currently support the adding of groups Major Resolved
CWD-313 The Apache module needs some kind of cache implemented similar to our other 'clients', to help improve performance around apache integration Major Resolved
CWD-305 Add optional GZIP compression support for XFire SOAP services and client. Major Resolved
CWD-304 Auto configure openid server as part of the setup process. Major Resolved
CWD-302 Skin the OpenID Server Major Closed
CWD-301 OpenID Client - Dummy Mode Major Resolved
CWD-300 OpenID Server - dummy mode Major Resolved
CWD-299 OpenID Client - Check Immediate Major Resolved
CWD-298 OpenID Server - Check Immediate Major Resolved
CWD-294 Test OpenIDClient Form Redirection Major Resolved
CWD-292 OpenID Server Implementation Major Resolved
CWD-291 Auto configure openid server as part of the setup process. Major Closed
CWD-290 Upgrade webwork from 2.2.4 to 2.2.5 Major Resolved
CWD-288 Change application titles - not footers Major Resolved
CWD-286 Skin Demo RP application Major Resolved
CWD-285 Display attributes in the demo application upon login (store in session for display) Major Resolved
CWD-284 Login and Logoff for OpenID demo relying party application. Major Resolved
CWD-283 Configure request attributes for demo app Major Resolved
CWD-280 Document OpenID server configuration Major Closed
CWD-279 Attribute/Profile Management Major Resolved
CWD-278 Authentication redirect from relying party. Major Resolved
CWD-277 Skin Server Major Resolved
CWD-276 Profile authentication history Major Resolved
CWD-275 Enable/disable localhost relying parties. Major Resolved
CWD-274 Whitelist and Blacklist Editor Major Resolved
CWD-273 Force Association Major Resolved
CWD-272 Reset password option. Major Resolved
CWD-269 document the management of the Crowd domain during setup and in the Console Major Resolved
CWD-246 Update documentation with new information about installing connector for 5.5.X version of JIVE. Major Resolved
CWD-232 add 'SecurityServerClient' Major Resolved
CWD-154 Apache DS connector Major Resolved
CWD-144 Add 'green' success message to 'update' actions on Console. Major Resolved
CWD-65 Explore OpenID support Major Closed
CWD-368 Stray backslash on Groups administration screen Minor Resolved
CWD-365 Typo in hint for Password Encryption during initial directory setup Minor Resolved
CWD-325 Directory details tab shows empty pink error box Minor Resolved

Cheers,

The Atlassian Crowd Development Team


Document generated by Confluence on Sep 04, 2008 00:44