Bamboo and Crowd SSO

Rumen Ginev

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

• integrating-bamboo-with-crowd

• integrating-crowd-with-atlassian-bamboo

• crowd domains

Also existing posts below did not help

• Bamboo-and-Crowd-SSO
• Bamboo-Crowd-SSO-and-SSO-Domain
• Bamboo-and-Crowd-SSO

 

From the Bamboo-and-Crowd-SSO above:

• Make sure Bamboo's crowd.properties 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!

 

Rumen Ginev

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:

• CWD-5352: session.tokenkey value randomly generated with quotes causing login issues to applications (fixed in Crowd 3.3.6, 3.4.5)