Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bamboo and Crowd SSO

I was able to configure Bamboo cetralised authentication with Crowd - pretty straightforward. However I cannot make SSO work.

Software versions I use are:

  • Crowd Version: 3.4.3
  • Bamboo Version: 6.9.0

I carefully followed instructions form

Also existing posts below did not help


From the Bamboo-and-Crowd-SSO above:

  • Make sure Bamboo's setup correctly: DONE
  • Make sure Bamboo's authenticator configured in seraph-config.xml is disabled and changed to Crowd's SSO authenticator: DONE
  • Make sure the domain configured correctly and Bamboo accessed using the same domain as other instances: DONE
  • Make sure that crowd-integration-client jar file version used by Bamboo is appropriate (Same as your Crowd version): Not required for Bamboo versions after 4.0
  • Check whether Bamboo sit behind a different proxy server as the others instances, if this is the case, make sure Bamboo's proxy server is added to Crowd: DONE

My experience is same as in Bamboo-and-Crowd-SSO. I can see that Bamboo generates new crowd.token_key.

Any suggestions/advice  would be greatly appreciated!


1 answer

1 accepted

2 votes
Answer accepted

Update: We were able to solve the issue with help from Atlassian Crowd Support team

Solution was upgrading to Crowd 3.4.5


This was caused by the known issue with Crowd placing quotes on the Crowd SSO cookie "crowd.token_key". We have since fixed this issue in Crowd 3.4.5:

I have to same issue as above but my version of crowd is 4.1.0 so quotes should not be an issue.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events