Jira cannot login with new Brave Browser

Dante Jauregui April 30, 2018

Good day team, 

there is a new browser that is really suitable for final users called BRAVE,used for blockchain too.

 

Can you solve the problem please? is not letting me get in with my login credentials, for a token storage problem, but actually this new kind of browser have as feature that...can you find a solution or version of attlassian for this new type of browsers? please

 

because the trend will be start using browsers like BRAVE

 

warm regards

 

10 answers

1 accepted

38 votes
Answer accepted
Ben Emmons September 24, 2019

Suggested workaround:

  1. go to: https://id.atlassian.com/manage-profile/profile-and-visibility
  2. disable shields
  3. go to https://yoursite.atlassian.net/
  4. disable shields
  5. go to brave://settings/shields
  6. Note the value for Cookie blocking and then set to 'Disabled'
  7. reload https://yoursite.atlassian.net/ (should now be logged in)
  8. go back to brave://settings/shields
  9. Set Cookie blocking value back to whatever your previous setting was..
  10. go to brave://settings/content/cookies
  11. in the "Allow" section click Add
  12. enter: [*.]atlassian.com
  13. click Add
  14. repeat 11-13 for [*.]atlassian.net and yoursite.atlassian.net

 

Want Atlassian to permanently fix this? Let them know! https://www.atlassian.com/company/contact/contact-ceos

Travis Dockter September 27, 2019

This is what worked for me

Like # people like this
Vladislav_Ermolaev September 30, 2019

Worked for me too. Thanks!

Malone Dunlavy October 1, 2019

If this doesn't work... 
One can manually add cookies to their Brave browser the same way they would with Chrome. Simply follow the instructions in this post: https://superuser.com/questions/244062/how-do-i-view-add-or-edit-cookies-in-google-chrome

I logged in on Chrome.
Settings>Privacy>View All Cookies
Searched for Jira. 
Copied the information into a string:
document.cookie="name=cloud.session.token; content=<enter string from Chrome cookie record>; domain=.jira.com; path=/; expires=<entertime> UTC"
Pasted the string in developer tools in Brave browser console and viola!

Prabhakar Battula October 30, 2020

Thanks! This worked.

Mike Bogucki October 30, 2020

I'm new to the brave-browser. How do you "disable shields"???

THnx

Ben Emmons October 30, 2020

Click the orange lion head to the right of the URL textbox and a popup will appear. If it says "Shields UP for this site" you click the toggle switch in the top right of the popup (looks like a horizontal lollipop) and it will disable Brave's shield protection for that site.

Mike Bogucki October 30, 2020

@Ben Emmons, Thank you, yes.. I figured it out after doing more googling. <My bad on my part.> 

Thank you again, esp for the speedy reply. 

Piyush Jaware November 11, 2020

Thanks a lot!

37 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 9, 2018

Update 27 Sept. 2019:

Welp, it looks like there have been changes to both Atlassian Cloud and Brave recently that renders my previous answer obsolete.   I would suggest that everyone take a look further down at @Ben Emmons recently updated answer on this post AND upvote his answer please :)   It contains current steps to help make this work in Brave today.  Rather than continue to update my answer, feels better to just give the proper credit to Ben here.

I also have cited Ben's answer on another question about this in https://community.atlassian.com/t5/Jira-questions/JIRA-is-not-working-on-Brave-Browser/qaq-p/1186772

Thanks Ben!

 

Updated 18 Sept 2019:

Due to changes on the ID site, the previous URL is redirecting to a different domain (start.atlassian.com) which made my old answer near impossible to complete.  I updated the URL to one that can be visited on that address that does not redirect.  Thanks to @Flosch for pointing that out.

 

Original answer:

I was playing with the Brave browse today and came across this same problem.    Even when I tried to whitelist my cloud site domain (example.atlassian.net) AND disabled the shields feature for my cloud site URL, I still could not login.

It turns out that Atlassian Cloud sites are also expecting a login call to happen to the https://id.atlassian.com domain.  And since this domain is different than the atlassian.net one, it still counts as a 3rd party site in the eyes of the browser (not really third party in the eyes of Atlassian).

I found that I first had to go to https://id.atlassian.com/manage-profile/profile-and-visibility and then in the brave browser, put the shields down for this site.  Once I did this on both that domain AND my Cloud site URL, I could login no problem.

Brave is interesting, it appears to be using the chromium engine on the backend.  So it might work just fine with Cloud as the official Google Chrome build would.  But it still is not technically supported yet by Atlassian.  Just something to keep in mind for the time being.

I hope this helps.

Andy

Gilberto Treviño August 22, 2018

Wow!!!  Great tip, thanks Andrew. Worked for me...

Like # people like this
Nélson Mourão September 28, 2018

Thank you, worked for me too!

Andrés October 23, 2018

It works!! Thanks for the tip! 👏🏻

nnyby November 7, 2018

Thanks Andrew. Just temporarily disabling Brave Shield on https://id.atlassian.com to complete the login process worked for me.

Like # people like this
Andy Bryant January 23, 2019

Thanks so much!

Michael Stamm April 24, 2019

Worked for me too. 

  1. Open https://id.atlassian.com, deactivate the Brave Shields for the site. 
  2. Open brave://settings/content/cookies and add https://id.atlassian.com 

Reload Confluence Tab which didn't work before, profit. 

Umar Qasim Qureshi April 26, 2019

Thanks it works.

Chandrahasa Kotyan May 15, 2019

Thanks for the tip. Worked like a charm

Nate July 12, 2019

Thank you!

Rachel Cox September 12, 2019

This doesn't work for me. I can "log in" but I can't see any projects.

Flosch September 18, 2019

This worked on one device, on another it didn't. Why?

Because you can't access company.atlassian.net (to deactivate Shield) if you're instantly hit with 14 redirects.

And you can't access id.atlassian.com (to deactivate Shield) if you're instantly hit with 8 redirects and end up on start.atlassian.com - apparently logged in enough to see your projects and tickets and your avatar in the bottom left, but not logged in enough to access company.atlassian.net! WTH, Atlassian.

Solution: go to chrome://settings/shields and allow all cookies. Then, go to company.atlassian.net. You should be logged in already or able to login. Afterwards, return your cookie settings to what you had before.

Like # people like this
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 18, 2019

Hi @Flosch 

Great call out. The ID site has recently made a number of changes and the redirects are aplenty.    I appreciate your own work-around here as well.  However there is also another way to reach the ID site without being redirected. 

Try visiting the URL https://id.atlassian.com/manage-profile/profile-and-visibility directly.   This specific address won't redirect users to the start.atlassian.com domain.  And from that profile page you can still put the shields down for the id site that way.

Thanks for the reply.   I will update my answer to reflect this change so it can continue to help other Brave browser users.

Andy

Like Flosch likes this
Rachel Cox September 18, 2019

@Flosch This was the first thing that worked. Thank you! But it only works if I keep the cookies setting on- "no cross-site cookies"-- If I turn cookies off completely it logs me out of Jira (and other things)

Flosch September 19, 2019

@Andy Heinzer Thanks for keeping your solution updated. :) You're saving a lot of people a lot of time.

@Rachel Cox Do you mean "Only block cross-site cookies"? Yeah, you can't deactivate all cookies if you want login on websites to work. "Only block cross-size cookies" is the default in Brave, so it's perfectly fine if you return it to that once you're logged into JIRA.

1 vote
Michael Coleman July 9, 2019

I got snagged on this just now and haven't managed to get past it.

 

Atlassian, do you want our business?!  Then fix your site.  This is the only one I deal with professionally that can't get this right...

Malone Dunlavy October 1, 2019

One can manually add cookies to their Brave browser the same way they would with Chrome. Simply follow the instructions in this post: https://superuser.com/questions/244062/how-do-i-view-add-or-edit-cookies-in-google-chrome

I logged in on Chrome.
Settings>Privacy>View All Cookies
Searched for Jira. 
Copied the information into a string:
document.cookie="name=cloud.session.token; content=<enter string from Chrome cookie record>; domain=.jira.com; path=/; expires=<entertime> UTC"
Pasted the string in developer tools in Brave browser console and viola!

0 votes
Azhar Khan April 20, 2021

None of the above solutions worked for me but the one mentioned on https://community.atlassian.com/t5/Jira-questions/JIRA-is-not-working-on-Brave-Browser/qaq-p/1186772 did i.e


1. Goto Site Data 

2. remove all Atlassian related cookies and site data

3. Now login again

0 votes
Patrick McKenna October 25, 2020

I'm still encountering this problem, despite trying to whitelist Atlassian-related cookies. Specifically, while leaving third party cookies blocked globally, I tried:

  • whitelisting all cookies, including third party ones, from *.atlassian.{net,com}
  • the same, but replacing the wildcards with specific subdomains. (In this case, I temporarily let the browser accept all cookies, logged in, then whitelisted each specific domain that had set 1+ cookie during the login process.)

In each case, I'd get stuck in an endless loop of redirects post-login. (I also tried clearing the cache and restarting the browser, but that didn't help.) The only solution that I found to work was enabling third party cookies globally, at the browser level.

This is an incredibly frustrating problem, particularly because, in using Brave for over a year now, I've never encountered it with any other site. That alone suggests to me that this is fundamentally a problem with Atlassian's authz implementation, not a browser issue. Yes, Brave tweaks Chromium to better preserve user privacy, but that doesn't seem to break any other site. Moreover, why should any site require a user to admit third party cookies (globally, at the browser level!) in order to login?

If someone has a better technical understanding of why this is happening, or workaround suggestions, I would really appreciate hearing them.

Andrew Pavlis October 26, 2020

This worked for me on Brave Version 1.15.76 Chromium: 86.0.4240.111 (Official Build) (x86_64):

  1. go to: https://id.atlassian.com/manage-profile/profile-and-visibility
  2. disable shields
  3. go to https://yoursite.atlassian.net/
  4. disable shields
  5. go to brave://settings/shields
  6. ensure id.atlassian.com and atlassian.com to the list and check accept 3rd party cookies

I didn't have to restart the browser, just reloaded the pages and it all worked.

0 votes
Olivier Crozier May 2, 2019

For me, what made it work, is only:

- To clear storage for https://id.atlassian.com (Open that URL then: F12 > Application > Clear storage > Clear site data), and

- To close and restart Brave browser (I did it twice, first time I got an oops).

No even need to update the White List and to deactivate the Brave Shields.

0 votes
Kayd Withers August 1, 2018

Me too, thanks heaps Andy.

0 votes
Kieran Conlon July 27, 2018

Cheers Andy.

Worked for me too.

It was getting very tedious having to remember to copy JIRA ticket links from e-mail updates and manually open in another browser.

0 votes
Deleted user June 19, 2018

Thank you Andy. Works for me

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 30, 2018

Atlassian code is built with standards in mind, not browsers.  They then commit to support the most popular browsers (supporting IE for example, despite its miserable failures to be a proper browser).

If Brave becomes a widely used browser, I'd expect Atlassian to support it.  But at the moment, it's not.  As it's a relatively new piece of software, I would be questioning why the browser is not supporting the standard way of logging in.  At the moment, this is a problem with Brave, not Atlassian.

You'll need to come up with a very strong business case to support a non-standard browser if you want Atlassian to code for it as well as the most popular browsers.

Shawn Whinnery August 7, 2018

If you'd take 4 seconds to google it you'd know that Brave is Chrome without telemetry. The case is that an enterprise customer prohibits the use of Google Chrome for security.

Like # people like this
Michael Coleman September 12, 2019

It's clearly the opposite.  If they were supporting the standards, instead of coding to specific browsers, this wouldn't fail.

Like Mark Hubbard likes this
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 28, 2019

<sigh> you really have not understood the point.  It fails when browsers don't behave to standards.

On the bright side, it should be a lot better soon, as Microsoft have finally admitted they have no idea how to write a browser (or anything else) and are going to adopt a chromium base.  Oh, and  slightly earlier than that announcement, Brave has said it is going to stop ignoring standards, so we should see improvements quite soon.

Suggest an answer

Log in or Sign up to answer