You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
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.