Both JIRA and CRUCIBLE are setup to use CROWD. Crucible was originally using JIRA's user directory. The user directory from JIRA got imported into Crowd and I see all the users in Crowd.
Now when logged in to JIRA click on a Code Review link it opens up the Crucible's page and clicking on 'Join The Review' asks me to login again. What am I missing?
I followed the steps in the document that you have attached ......
>>>1.Ensure that each application is using at least version 2.0 of the crowd-integration-client JAR file for interoperability. For more information, please review this Knowledge Base article.
yes, I have version crowd-integration-client-2.4.0.jar
>>>2. Confirm that you can log in to each application with the same username and password.
confirmed. The authentication test from CROWD for crucible successfully passed.
>>3.Set each application to use centralised SSO authentication, as follows. Ensure that each Atlassian application's WEB-INF/classes/seraph-config.xml file is using the Crowd's com.atlassian.crowd authenticator class. For example in JIRA, instead of this:
There is no seraph-config.xml file under my C:\fecru-2.7.12\content\WEB-INF\classes folder ( or anywhere under fecru-2.7.12 folder).
could this be the problem?
It is working now.
This is what I did....
First of all, I enabled the DEBUG logging for Crowd and compared the log between direct login to CRUCIBLE while logged in to JIRA in another window (which worked fine ) and navigating to Crucible from within JIRA Issue (which didn't work) that led me to try the following....
All my servers are 'localhost' but the Crucible url that is being used by JIRA when 'Create Review' is clicked within JIRA is using the machine name instead of localhost ie http://test-srv-13:8060 instead of http://localhost:8060.
I added 'test-srv-13:8060' to the 'Remote address' list within Crowd's application browser/RemoteAddresses list. With that now I able to create review from JIRA in Crucible without having to login again.
It is working now.
I enabled the DEBUG logging for Crowd and compared the log between (i) direct login to CRUCIBLE while logged in to JIRA in another window (which worked fine ) and (ii) navigating to Crucible from within JIRA Issue (which didn't work) that led me to try the following....
All of my applications(Jira, Crucible etc) are using 'localhost' in the url but the 'localhost' was not present under Crowd's RemoteAddresses list for Crucible.
Adding which resolved the issue.
Though this took care of the main issue here then noticed that when I click on an existing Code Review link within JIRA it was asking me to login again...
'Create Code Review' link's url within JIRA --> http://localhost:8080/browse/TST-2?page=com.atlassian.jirafisheyeplugin:fisheye-issuepanel# ( this works)
Existing Code Review link's url within JIRA .... ( the ones not working)
CR-1 link --> http://test-srv-13:8060/cru/CR-1
For this I changed the 'display url' for Crucible in JIRA's application link setting to http://localhost:8060 and that took care of the second issue.
What I don't understand is why the second issue even happened though I have both http://test-srv-13:8060 and http://localhost:8060 listed under 'Remote addresses' list for Crucible in Crowd.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs