Crucible Error: Exception encountered while contacting JIRA Server: User not authenticated yet, or session timed out.

Has anyone seen this error in Crucible (in a review body plus in the header plus in the close review screen)?

Exception encountered while contacting JIRA Server Author-it JIRA: User not authenticated yet, or session timed out.

and know how to troubleshoot it?

I'm trying to set up the 'transitioning a linked issue' and test it, but its failing with this message when trying to retrieve the status. It also shows in the review body.

What is weird is that the JIRA issue link shows up with this message beside it, but I can click the link and go to the ticket in JIRA whilst using my same log in. I can also click the Crucible link in JIRA for the same issue and go back to Crucible. It would appear the application linking is working, except for this error message and I assume that it should be displaying the issue summary instead of the error message. My biggest problem is that I can't use the transition linked issue functionality.

Thanks!

2 answers

1 accepted

Accepted Answer
0 votes

Actually..

I was concerned about using basic authentication because the password for the account can easily change, also because it appears that when it is configured in this way, the user that shows in JIRA as making status updates to the tickets via Crucible is the one that you have configured in the basic authentication settings in the application link. It needs to be the actual user closing the reviews.

So..

I removed the application links and started again. I also re-did the LDAP integration in Crucible. I've set up the application link so that it only uses Oauth, since although my user base is the same, each application is individually integrated with LDAP. I then rechecked that only oauth was being used, logged in as me, told Crucible it was allowed to use my access to get to JIRA and vice versa in JIRA (review/source tab in the tickets) and then also tested this with another user. Doing this seems to have fixed the problem. I believe it was having trouble knowing what to do as both trusted applications and oauth were configured in the application linking and then since they were, it required (for some reason) basic auth to be set up.

So everything is now working! Bottom line it appears its best only to have one method of authentication set up in the application link, but of course I'd imagine this depends on how closely related your users and usernames are.

ok, managed to fix this. I had to configure the basic authentication in the application link to JIRA. Not sure why this was suddenly required. Jira 5.2 and Crucible 2.9.1. We use AD, so will have to check it again when my password changes.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Featured Groups

Tuesday tips & tricks: What is the Atlassian Community?

It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...

44 views 2 4
View post

Atlassian User Groups

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!

Find my local user group

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

Groups near you