Crowd allows the use of custom SSO cookie names, to enable segmentation between application zones. The default is "cookie.token_key" but it can be overiden in configuration.

From the crowd wiki documentation: (http://confluence.atlassian.com/display/CROWD/The+crowd.properties+File)
(setting) cookie.tokenkey
(descirption) When using Crowd for single sign-on (SSO), you can specify the SSO cookie name for each application. Under the standard configuration, Crowd will use a single, default cookie name for all Crowd-connected applications. You can override the default with your own cookie name.
As well as allowing you to define the SSO cookie name, this feature also allows you to divide your applications into different SSO groups. For example, you might use one SSO token for your public websites and another for your internal websites.
(default value) crowd.token_key

Please enable setting a custom SSO cookie name so that we can use the SSO features.

Comments

ebeyrent’s picture

Assigned: Unassigned » ebeyrent
rjacobs’s picture

Title: Does not allow custom SSO cookie name » Allow custom SSO cookie name to be configured
Version: 6.x-1.x-dev » 7.x-2.x-dev
Assigned: ebeyrent » Unassigned

Hummm, this is an interesting point, and one that should probably be addressed. Now that focus is shifting to the 2.x branch I'm thinking that it makes better sense to move this there.

rjacobs’s picture

Status: Active » Fixed

I just committed a change that allows the cookie name and duration to be configured. Here's the commit for D7:

http://drupalcode.org/project/crowd.git/commit/6367f66

And for D6:

http://drupalcode.org/project/crowd.git/commit/47b7a51

Status: Fixed » Closed (fixed)
Issue tags: -SSO cookie crowd.token_key

Automatically closed -- issue fixed for 2 weeks with no activity.