Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2625

One domain use by multiple Crowd should not blocked the SSO function

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Customers usually have two set of instances on their environment, each for production and QA purposes.

      Some company would prefer to set their environment for both QA and production on the same domain. However this would result to signing out the others set of instances when a user log-in to the other set of instances.

            [CWD-2625] One domain use by multiple Crowd should not blocked the SSO function

            shihab added a comment -

            You can do this by changing the name of the cookie (cookie.tokenkey)client applications use to store the SSO token: http://confluence.atlassian.com/display/CROWD/The+crowd.properties+File

            So in your specific case, set crowd.tokenkey=crowd.qa.token_key for your QA apps.

            shihab added a comment - You can do this by changing the name of the cookie (cookie.tokenkey)client applications use to store the SSO token: http://confluence.atlassian.com/display/CROWD/The+crowd.properties+File So in your specific case, set crowd.tokenkey=crowd.qa.token_key for your QA apps.

              Unassigned Unassigned
              ad9744759bcd Honeywell JIRA Admin
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: