Hi,
Our setup is CROWD + JIRA + Confluence. SSO for CROWD and confluence is fine. I have tried all things i found but to no avail. Also enabled DEBUG logging in CROWD with no additional info.
I traced the issue to the cookie domain being written. When I was trying SSO and forgot to add the SSO domain in Crowd, the cookie when logging into JIRA was from jira.xxx.comand the cookie from Confluence was confluence.xxx.com. After updating the SSO domain, confluence changed the cookie to .xxx.com. Jira changed to .jira.xxx.com.
Strangely when i do some actions, a cookie from crowd with the correct domain appear.
Has anyone encountered this issue or can suggest some places to investigate?
Hi Aldo, in case you see the cookie does not contain the same information when logging with Confluence comparing to JIRA, the following questions usually help to identify what's wrong:
What are the URLs being used to access each application?
What is the SSO Domain
value stored in Crowd?
Are both applications using the Crowd authenticator at their WEB-INF/classes/seraph-config.xml files? Are all the configuration inside crowd.properties correct?
How many Directories are assigned to each application in Crowd? If more than one, are they in the exact same order
?
Are proxy servers being used between Crowd and the applications? If so, please add their IP addresses to the Trusted Proxy Servers list
in Crowd.
Additionally, you can check the logs with debug enabled to get more information about this issue:
Under Admin -> Logging & Profiling in Crowd, change the com.atlassian.crowd
package
to DEBUG.
Replicate the problem you are having (Logoff from all the apps; Login to your third-party and then
try
to access JIRA; Logoff again from all the apps; Login to JIRA and then
try
to access your third-party app).
Check the results into atlassian-crowd.log
file.
I hope this helps
Cheers
Hi Tiago,
I tried adding DEBUG information but without success... I forgot to mention that the system is on a Windows Environment.
The issue was due to IIS configuration. We dont have time to see what was wrong with the configuration is ARR and we replaced IIS with Apache and SSO is working now.
Thanks for your time,
Aldo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.