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

Crowd behind IIS reverse proxy - no SSO

hoon oh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 5, 2012

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

0 votes
Wesley Woo
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 16, 2013

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

0 votes
Tiago Comasseto
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.
April 30, 2013

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
Rodrigo Girardi Adami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 30, 2013

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
AUG Leaders

Atlassian Community Events