The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bonfire not playing nice with JIRA 4.4.3 + Crowd 2.2.7 SSO

charleslcso
Contributor
October 10, 2012

Whenever I try to log into JIRA via Bonfire extension, and as long as I have already logged into JIRA via another tab in the same browser, Bonfire extension will complain a 401.

I have to log out from the JIRA tab, before I can log into JIRA thru Bonfire.

This is not very nice... because usually we work on multiple projects in JIRA.

Is it by design?

Bonfire 2.3.1.0 extension.

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
FagnerF
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 Champions.
November 11, 2012

Hi Charles,

I believe it's not by design, at least I don't think so.

What is the current Bonfire version? Is it happening in any browser?

Have you tried to use another browser?

It can may be some browser issue. You can check out in Bonfire Compatibility Chart.

I hope it helps

charleslcso
Contributor
November 16, 2012

Hi Fagner

Originally I think it should not be designed like this. It happens on all browsers.

Annoying. Very annoying.

We wont upgrade to a latest version of JIRA, Confluence or Bonfire. We'll have to live with Bonfire 2.3.1.0.

0 votes
charleslcso
Contributor
November 16, 2012

See comment

TAGS
AUG Leaders

Atlassian Community Events