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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,633
Community Members
 
Community Events
176
Community Groups

Crowd behind IIS reverse proxy - no SSO

Hi,

I am rather technical novice with a web server and I am trying to setup JIRA, Confluence and Crowd with IIS reverse proxy within a single server. I followed the installation documents and successfully enabled all of these services with sub-domains, with some help with the method I found from a user comment within the documentation.( http://willhughes.me/20100112/jira-fisheye-and-iis7-using-application-request-routing/ )

The last problem is that SSO doesn't work within the three Atlassian products, while the Google Apps SSO worked flawlessly.

It is a bit odd that with the com.atlassian.crowd logging set to DEBUG or ALL, I am not getting any outputs when I open up the main page of JIRA or Confluence. (or could this be normal?)

Any help will be appreciated. Thanks!

3 answers

Exactly the same problem here, no SSO for Crowd, Confluence and JIRA behind IIS8 with ARR3 as reverse proxy.

0 votes

Hi,

I'd also suggest that you take a look that the key points for enabling Crowd SSO in this other question.

Cheers

0 votes

Hi there!

I'm not very keen at reverse proxies configuration, however this could be causing some problem to the SSO cookie. Can you confirm the SSO worked before setting the reverse proxy?

If yes, then some rule in the proxy could be messing with the SSO. What you can try to do to troubleshoot this is to enable the debug logging into Crowd instead.

  1. In Crowd, go to 'Administration' -> 'Logging & Profiling'. Change the com.atlassian.crowd package to DEBUG.
  2. Replicate the SSO problem you are having.
  3. The new info should be inside the Crowd logs located at {CROWD HOME}/logs/atlassian-crowd.log}. If you need some additional help to debug the file, please raise a support ticket to us!

I hope this helps!

Rodrigo

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events