CORS Issue with atlassian.net
See original GitHub issueLooks similar to 2252 but that is Closed.
Description
Unable to login to JIRA at https://<mycompanyname>.atlassian.net
because of CORS issue.
Steps to Reproduce
Attempt to login to JIRA.
Actual result:
Dev tools console shows this:
Access to fetch at 'https://mgas.prod.public.atl-paas.net/analytics/event' from origin 'https://<mycompanyname>.atlassian.net' has been blocked by CORS policy: Request header field content-type is not allowed by Access-Control-Allow-Headers in preflight response.
Expected result:
I can login to JIRA.
Reproduces how often:
Happens every time. Doesn’t happen with other browsers.
Brave version (brave://version info)
Brave | 0.63.55 Chromium: 74.0.3729.131 (Official Build) (64-bit) Revision | 518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954} OS | Windows 10 OS Build 17134.648
Version/Channel Information:
- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? Unknown
- Can you reproduce this issue with the dev channel? Unknown
- Can you reproduce this issue with the nightly channel? Unknown
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? No
- Does the issue resolve itself when disabling Brave Rewards? No
- Is the issue reproducible on the latest version of Chrome? No
Miscellaneous Information:
none
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
CORS error with Jira REST API on Cloud - Atlassian Community
I'm attempting to write a script that will run from my local webserver and get a list of projects on my Jira cloud...
Read more >How can I solve the CORS error when accessing the Jira API?
Solved: Hey folks, I am working on a small Figma plugin and would like to access information (status, name) of Jira tickets. However,...
Read more >Getting CORS errors when accessing Confluence resources
When accessing Confluence resources from another origin, the request is blocked and may result in a CORS error similar to the following:.
Read more >CORs error with REST api - Jira Cloud
I'm trying to call the REST api via a javascript ajax call and getting a CORS error. I've searched community.atlassian.com, but all of...
Read more >Cross Origin Resource Sharing (CORS) issue with JIRA ...
JIRA CLOUD doesn't allow cross origin requests. You'll need a proxy service between the apps to connect to JIRA CLOUD REST API. Currently...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@btlechowski would be good to test - if it works on Release channel too, then I think we can remove milestone and put
Release Notes/exclude
. If the whitelist update (which happened to 0.72.x) resolves this, then we can mark asRelease Notes/include
and keep milestoneVerified passed with
Reproduced issue using version 0.63.55. Upgraded to 1.1.5 and verified I was able to login without issue. 0.63.55: 1.1.5:
Confirmed able to login to Jira/Atlassian on clean profile with 1.1.5 as well.
Verification passed on
Verified using jira credentials and google account
Verification passed on