Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CORS Preflight did not succeed on custom Jira server #352

Closed
8 tasks done
bergerst opened this issue Mar 1, 2024 · 1 comment
Closed
8 tasks done

CORS Preflight did not succeed on custom Jira server #352

bergerst opened this issue Mar 1, 2024 · 1 comment

Comments

@bergerst
Copy link

bergerst commented Mar 1, 2024

Checklist before you being

  • I am sure that I am already using latest version of Jira Assistant
  • I had verified that, no similar issues are already reported in issue tracker
  • I had tried reproducing this issue with with Web version of Jira Assistant to ensure that this issue is not recently fixed and yet to be published
  • I had verified that, my query is not answered in FAQ section of website
  • I had verified that, my issue is not listed as known bugs in website

How do you use Jira Assistant?

Browser extension

Are you using cloud version of Jira or self hosted (data center / server) of Jira.

Self hosted (datacenter)

Version of Jira Assistant

v2.58

What browser are you using?

Firefox

What OS are you using? You need not disclose this if you feel it is irr-relevant for your issue.

Windows

Bug Description

I am trying to set up Jira Assistant for my company's Jira server and getting this error in the network logs.

image

Previously I faced another CORS error until I added moz-extension://5bb4c444-5db8-4384-a9b4-6fa21bd381e3 to the server's CORS Allowlist.

Here are the failing request and response:

OPTIONS /rest/api/2/myself HTTP/1.1
Host: jira.xxx.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Access-Control-Request-Method: GET
Access-Control-Request-Headers: content-type,user-agent
Origin: moz-extension://5bb4c444-5db8-4384-a9b4-6fa21bd381e3
Connection: keep-alive
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site
HTTP/1.1 401 
Server: nginx/1.14.1
Date: Fri, 01 Mar 2024 12:53:09 GMT
Content-Type: application/xml;charset=UTF-8
Content-Length: 148
Connection: keep-alive
X-AREQUESTID: 833x1439853x1
Referrer-Policy: strict-origin-when-cross-origin
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: sandbox
Strict-Transport-Security: max-age=31536000
Set-Cookie: atlassian.xsrf.token=B1PI-S9BJ-TZKJ-5N13_da9fa7d85a92217a10324b940fd3186b74a64109_lout; Path=/; Secure; SameSite=None
X-AUSERNAME: anonymous
Cache-Control: no-transform
Access-Control-Allow-Origin: moz-extension://5bb4c444-5db8-4384-a9b4-6fa21bd381e3
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Origin, Authorization, Content-Type
Vary: User-Agent
WWW-Authenticate: OAuth realm="https%3A%2F%2Fxxx.com"
Content-Encoding: gzip

Chrome and Edge work on my machine.

Checklist before you submit

  • I have ensured not to paste any confidential information like Jira url, Mail id, etc.
  • I have verified my browser console logs and added necessary details (if required)
  • I have added required screenshots if the bug is related to UI (as necessary)
@bergerst
Copy link
Author

bergerst commented Mar 4, 2024

Was able to resolve the issue by enabling these options in about:addons -> Jira Assistant -> Permissions

image

@bergerst bergerst closed this as completed Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant