Documentation for Crowd 2.3. Documentation for other versions of Crowd is available too.
The core Crowd functionality supports SSO across applications within a single domain, such as Example 1: If you wish to have single sign-on (SSO) support for *.mydomain.com, you will need to configure the SSO domain in Crowd as Crowd JIRA Confluence FishEye FishEye in different domain Example 2: If you wish to have single sign-on (SSO) support for mydomain.com/*, you will need to configure the SSO domain in Crowd as Crowd JIRA Confluence FishEye FishEye in different domain You can find information the comparison of host name strings in RFC 2965 (pages 2 and 3).*.mydomain.com. Crowd uses a browser cookie to manage SSO. Because your browser limits cookie access to hosts in the same domain, this means that all applications participating in SSO must be in the same domain..mydomain.com — including the full stop ('.') at the beginning. All your Crowd-connected applications must be in the same domain. For example:
crowd.mydomain.com 
jira.mydomain.com
confluence.mydomain.com
fisheye.mydomain.com
fisheye.example.com 
mydomain.com. All your Crowd-connected applications must be in the same domain. For example:
mydomain.com/crowd
mydomain.com/jira
mydomain.com/confluence
mydomain.com/fisheye
example.com/fisheye
RELATED TOPICS
Overview
Content Tools
Apps
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.