Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Enable SSO with crowd on different machine

I have crowd on one machine and other atlassian tools on different machine.

Can i enable SSO in my this senerio ?

I have done all configuration according to the crowd integration documentation (with jira,confluence,stash and bamboo), but SSO is not working.

My tools are not in same domain and i am not using any proxy server also. Only crowd is on different machine except that all the tools are on same machine.

Is it necessary that crowd and other tools should be in same domain ?

1 answer

Hi Manjul, there should be no problem in having the applications on different machines, but the doman may cause problems with the SSO. You may want to check this doc for more information about the domain format.


Hi Tiago,

Thanks for your response.

So, for SSO to work properly all the tools should be in same domain including crowd ?

In the doc suggested by you, it is mentioned that we can leave SSO domain empty. What will happen in that senerio ?

Hi Manjul, that's correct, the domain should be the same. You can use the domain format you prefer though (.mydomain or mydomain/app).

Also, if you leave the domain field empty, the SSO cookie in your browser will be created with the domain of the application that made the request to Crowd, but the important part is that if another application try to authenticate to Crowd with a different domain than the first application, the initial cookie won't be used and the SSO won't work.


Hi Tiago, as i mentioned in my above conversation that except crowd all atlassian tools are on same machine. So according to that SSO cookie that will generate on browser will generate on the basis of that machine's (on which jira,confluence,stash and bammboo are installed) IPAddress, right ?

So, SSO should work for all tools (jira,confluence,stash and bamboo) except crowd (as crowd is on another machine).

Hi Manjul, in fact the SSO cookie will be created based on the URL of the applications, not the IP. Your applications can be installed on different machines with different IPs and the SSO would still work.

The important part is that the URL of the applications should match the domain format of the previous doc.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

306 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you