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

Crowd SSO Invalid Domain

Maggie June 10, 2020

I use Crowd Server to administer security for Jira, Bitbucket, Confluence, & Bamboo. I'd like to set up single-sign on via Crowd, but I'm having problems with the SSO instructions.

Base Url: http://localhost:8095/crowd

User Url: http://[servername]:8095/crowd

SSO Domain: [servername]/* OR [servername]:8095/*

Crowd rejects both of the above SSO Domain options. I've reviewed the set up instructions, including the IETF's RFC 6265 document. As far as I can tell, this is what my SSO Domain should be set to. I've tried updating the cwd_property table in the SQL database, as well, but that basically locks me out of the Crowd UI. Do this SSO Domain need to have a ".com" suffix? This server is internally hosted, so all of our users reference it as "http://[servername]" when authenticating to it. What am I missing?

Any help would be most appreciated!


Crowd Version 4.0.0

Java JDK & JRE Version 8

1 answer

0 votes
Bruno Vincent
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 13, 2020

Hello @Maggie 

I guess [servername] is something like myserver.mydomain (e.g. crowd.intranet.local)

In such a case, the SSO Domain to be set in Crowd's console is mydomain (e.g. intranet.local)

Thus, whenever a user browses to jira.intranet.local / bitbucket.intranet.local / confluence.intranet.local / bamboo.intranet.local their browser sends a Crowd SSO cookie that is valid for the intranet.local domain (BTW as you can guess from that example, the domain name does not need to have the ".com" suffix).

Hope this helps.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events